Log Aircall call summaries to HubSpot and flag risky calls in Slack

Trigger: an Aircall webhook on the Conversation Intelligence summary.created event, which fires once Aircall has finished analyzing a completed call. This workflow only makes sense when the Aircall Conversation Intelligence add-on is enabled — without it, the transcription, summary, sentiment, topics, and action-item endpoints return 403 and the run will fail.

When the webhook fires:

1. Use the call id from the webhook payload to pull the full picture from Aircall. Call Retrieve a Call to get the caller and callee phone numbers, direction, agent, duration, and the call's Aircall URL. Then call Retrieve Call Summary, Retrieve Call Sentiments, Retrieve Call Topics, Retrieve Call Action Items, and Retrieve Call Transcription. Treat the transcription as background context for reasoning — it does not need to go into the CRM note verbatim.

2. In HubSpot, find the matching contact using Search Contacts. Match on the customer's phone number against the phone, mobilephone, and hs_calculated_phone_number properties (normalize to E.164 first, and also try the last-10-digits form so number formatting differences don't miss the match). If more than one contact matches, prefer the one most recently engaged. If nothing matches, skip the HubSpot note step and instead post a short Slack message to the designated account-management channel asking a rep to add the contact, then still leave the Aircall comment described in step 4.

3. Create a HubSpot Note (Create Note) associated with that contact, and also associated with any open deal on the contact if one exists. The note body should include: the Aircall call summary; the overall sentiment label and numeric score; the list of key topics as tags; a bulleted list of action items with owner and due-date hints where Aircall provided them; and a link back to the original call in Aircall. Keep formatting light — a short header, one paragraph for the summary, then bulleted sections.

4. Comment back on the Aircall call using Comment a Call with a short line linking to the HubSpot contact record (and the deal, if a deal was associated). This closes the loop so anyone reviewing the call in Aircall can jump straight to the CRM.

5. Decide whether to alert. Send a Slack message (Slack Bot, Send a Message) to the designated account-management channel if either of these is true: the overall sentiment is negative (or the score falls below a configurable threshold), or any action item is flagged urgent/high priority in Aircall's output. The Slack message should include the contact name, the deal name if any, the sentiment score, one-line summary, the top action items, and links to both the HubSpot record and the Aircall call so a rep can pick it up same-day. Do not send the Slack alert on neutral or positive calls.

Nice-to-haves: dedupe by call id so a webhook retry doesn't create duplicate notes; if the HubSpot contact has an owner, mention that owner in the Slack alert; and when the call was inbound to a specific Aircall number that maps to a team, route the Slack alert to that team's channel instead of the default one.