Use a webhook when an external system should add contacts to a Continuous Calling campaign. Each accepted request adds a call to the campaign queue; the campaign cadence determines when that call can run.
Phonely does not deduplicate accepted webhook requests. If the sending system retries a request, it can queue another call. Prevent duplicate requests before sending them when one contact should produce only one call.
- Create or edit a Continuous Calling campaign.
- In Select Trigger Type, choose Webhook.
- Copy the generated webhook URL and authorization details.
- Define the JSON request body, then select Set Fields.
- Map the detected fields to the contact phone number, optional timezone, dial-out number, or calling window, and any variables used by the outbound flow.
The default body includes phone_number, timezone, dialout_number, and calling_window. You can add fields required by your flow.
A calling_window narrows the campaign’s calling hours for that contact only. See calling windows.
Send JSON with the authorization required by the generated webhook. Keep the credential private and do not place it in client-side code, screenshots, or documentation examples.
Keep the schema aligned
Select Set Fields whenever you add, rename, or remove a top-level field. Then review the campaign mappings and any downstream flow fields that use those values.
Verify the trigger
Use a phone number you control and send a representative request. Confirm that:
- the call appears in the campaign queue;
- the phone number, timezone, and optional dial-out number or calling window resolve correctly; and
- the selected flow receives the expected mapped values.
Testing the webhook can queue and place a real outbound call when the campaign is running. Last modified on August 18, 2026
