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

# Log call dispositions after a dialing block

Spion recorded this as a manual browser process (8 steps, ~25 min, daily) and redesigned it as a consolidated automation (4 steps). Build the OPTIMIZED workflow below, not a replay of the manual clicks.

Overview: Read an Outreach dialing session, draft a disposition and one-line summary per contact, write to Salesforce, and set the next task.
Tools: Outreach, Salesforce, Claude
Trigger: After a dialing session (When an Outreach dialing session ends).
Efficiency target: 8 manual steps down to 4 (50% fewer), saving ~25 min per run, about 90 hours a year.

## Optimized workflow steps

1. [Outreach] Read session
   What: Read every contact and call note from one dialing session.
2. [Claude] Draft disposition and summary (added by Spion: net-new value)
   What: Classify each call (Connected, No answer, Left voicemail, Not interested, Meeting booked) and write a one-line summary from the notes.
   Why: turns raw notes into a clean, consistent CRM record.
3. [Salesforce] Update record
   What: Write disposition, last activity, and a logged call with the summary.
4. [Salesforce] Create task
   What: Create the next-step task with a due date by disposition: callback in 2 days, recap today, or nurture in 30 days.

## Original manual process (reference only, do not replicate)
1. Open the dialing session
2. Re-read notes per contact
3. Pick a disposition
4. Type a summary
5. Update Salesforce
6. Set the next task
7. Repeat per contact

## 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. Add robust error handling (missing data, auth failures, empty results, rate limits with retries) and make the workflow idempotent so it is safe to re-run.
7. Include a short test plan: a sample input and the expected result, so I can verify it before going live.
8. Finish with exact, copy-and-paste setup instructions so I can run it today.