You are a senior automation engineer. Build the following optimized workflow.

# Summarize customer calls into CRM notes & next steps

Spion recorded this as a manual browser process (5 steps, ~15 min per call, several a day) and redesigned it as a consolidated automation (3 steps). Build the OPTIMIZED workflow below, not a replay of the manual clicks.

Overview: After a customer call, turn the transcript into a clean account note, a list of action items with owners, and any risk or expansion signal — written straight back to the CRM so the CSM never retypes a recap.
Tools: Gong (or Zoom), Claude, Salesforce (or HubSpot)
Trigger: Recording event (When a customer call recording is ready).
Efficiency target: 5 manual steps down to 3 (40% fewer), saving ~15 min per call.

## Optimized workflow steps

1. [Gong] Read the call
   What: Read the transcript, participants, account, and call type.
2. [Claude] Summarize and extract (added by Spion: net-new value)
   What: Write a five-line recap; list action items with an owner and due date; tag any churn-risk or expansion signal with the supporting quote.
   Why: turns an hour of conversation into a CRM-ready record and a follow-up list, consistently.
3. [Salesforce] Write back
   What: Append the recap to the account timeline, create the action items as tasks, and set a risk/expansion flag the health report can read.

## Original manual process (reference only, do not replicate)
1. Open the call recording
2. Re-listen / skim the transcript
3. Type a recap into the CRM
4. Create follow-up tasks
5. Flag the account if at risk

## What I need from you
1. Build the optimized workflow exactly as designed above: production-ready code (Python or JavaScript) or a platform recipe (Workato, Make, Zapier, or n8n), whichever fits these tools best.
2. Preserve the consolidation. Do not expand it back into the manual click-by-click process.
3. Recommend the right trigger and cadence (schedule, webhook, or event). If it recurs, state the exact schedule.
4. Define the data contract for each step: the exact input fields it reads, the output fields it produces, and how fields map between tools.
5. Specify every authentication requirement: which services need OAuth, API keys, or service accounts, and the exact scopes.
6. Keep the recap faithful to the transcript — no invented commitments or numbers — and leave the account note editable so the CSM can confirm before it's shared.
7. Add robust error handling (missing transcript, auth failures, empty results, rate limits with retries) and make the workflow idempotent so it is safe to re-run.
8. Include a short test plan: a sample transcript and the expected note + tasks, so I can verify it before going live.
9. Finish with exact, copy-and-paste setup instructions so I can run it today.