Quickstart
This quickstart builds the smallest complete phone-system loop: create an action called Interested, receive the webhook when an agent applies it, then add a post-call disposition so the workflow has a required final classification.
You will finish with:
- One action outcome agents can use during a call.
- One signature-verifying webhook receiver that returns
2xx. - One disposition outcome that turns on the post-call disposition step.
Prerequisites
- A Sailor API key created by an owner or admin in Settings → Integrations → API access. Production keys begin with
sl_live_and are revealed once. - A Smart List ID from the workspace you want to update.
- An HTTPS endpoint that can receive
POSTrequests. - A webhook signing secret created in Settings → Integrations → Webhook signing.
1. List Existing Outcomes
Start by reading the current configuration.
The response includes disposition_popup_enabled. It becomes true when at least one post-call disposition outcome is configured.
2. Create An Action Outcome
Action outcomes are available during a live call. They require a webhook_url because Sailor posts an event when the action runs.
Sailor returns 201 Created with the created outcome and the current disposition_popup_enabled value.
3. Receive The Webhook
Your endpoint should accept a JSON body and return any 2xx status.
Do not process an unverified body. After verification, persist the unique X-Sailor-Delivery-Id, return 2xx, then do slow downstream work asynchronously.
4. Add A Post-Call Disposition
Disposition outcomes are shown after a call. Use them for required post-call classification.
After this, GET /phone-system/outcomes should return disposition_popup_enabled: true.
5. Verify The Loop
Done When
Next Steps
- Read Core concepts for outcome types and destinations.
- Use Outcomes for update and delete examples.
- Use Webhooks for payload details.
- Use Rate limits to implement bounded retries.