Turn Aircall discovery calls into Notion CRM pages

Trigger: an Aircall webhook fires whenever a call is tagged. Only proceed if the applied tag matches the configured discovery tag list (default: a single tag named "discovery", but the author should expose this as a configurable list so ops can add "intro", "qualification", or whatever their team uses). Ignore every other tag event.

Once triggered, act as an SDR-turned-analyst: pull the Aircall Conversation Intelligence data for that call, resolve the caller to a contact, then file a fully written CRM page in a Notion database so the account manager never has to copy-paste from Aircall again.

Step 1: gather the call data from Aircall using the call id in the webhook payload. Call Retrieve Call Summary, Retrieve Call Transcription, Retrieve Call Sentiments, and Retrieve Call Action Items. If Conversation Intelligence is not enabled the endpoints return 403 — surface that clearly rather than writing an empty Notion page.

Step 2: identify who the call was with. The Aircall call payload includes the external number and (usually) an email; use Search Contacts (phone or email) to find the matching contact record. Read company name and the assigned Aircall user (the rep) off the contact. If no contact matches, still create the Notion page but flag it clearly so the rep knows to fill in the missing company/contact fields.

Step 3: inspect the target Notion CRM database. The Notion database is a customization: the author must ask the user which database to write into and then Retrieve a Database to read its schema. Map the workflow's logical fields (company, contact name, deal stage, sentiment score, next-step date) to whatever the actual property names are in that database, and warn if any expected property is missing. Do NOT hard-code property names.

Step 4: dedupe by company. Query a Data Source against the CRM database filtered by the company name. If exactly one page already exists for that company, create the new call page as a child of that page (parent = that page id) instead of as a top-level row in the database. If no page exists, create a new top-level page in the database. If multiple company pages exist, prefer the most recently edited one and note the ambiguity in the page body.

Step 5: build the page. Properties: company (from the contact), contact name (from the contact), deal stage (default to "Discovery" or the closest option in the database's stage select), sentiment score (from Retrieve Call Sentiments — normalize to whatever the database uses: number, select, or emoji), next-step date (extract from the summary or action items — the earliest concrete follow-up date; leave blank if none). Body content, in order: a short recap paragraph derived from the Aircall summary; a "Pain points" section with 2 to 5 bullet items, each a verbatim quote from the transcript with the speaker attributed; an "Action items" bulleted list the agent extracts from the transcript and Retrieve Call Action Items output; a footer with the Aircall call id and a link so someone can jump to the original recording.

Style rules for the page body: quote pain points verbatim (don't paraphrase — the value is that the account manager sees the exact words the prospect used). Action items should each start with a verb and name an owner where possible. Keep the recap under 150 words.

Idempotency: if the same Aircall call id has already been written into Notion (check for a small "Aircall call id" property or a body marker), don't create a second page — update the existing one or exit cleanly.