Integrations

Autopilot Journeys and Ortto Webhooks

Autopilot Journeys, now part of Ortto, can call an external endpoint when contacts reach a journey action and can send activity streams to custom endpoints.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • Legacy journey actions can batch up to 200 contacts in the records array.
  • Webhook actions support custom headers, HTTP Basic Auth, and custom payloads.
  • FastHook checks a configured Authorization secret before accepting the payload.
  • The legacy webhook action waits five seconds and retries only two additional times.

Create the FastHook source

Create AUTOPILOT source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Autopilot Journeys and Ortto Webhooks",
    "type": "AUTOPILOT",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "AUTOPILOT",
        "webhook_signing_secret": "autopilot-authorization-secret"
      },
      "allowed_http_methods": ["POST"]
    }
  }'

Setup

  1. Create an AUTOPILOT source and save a strong Authorization secret.
  2. Add a webhook action to the required Autopilot or Ortto journey step.
  3. Use the FastHook Source URL and configure Authorization: Bearer YOUR_SECRET.
  4. Run a test contact through the journey and inspect records, journey, and custom payload fields.

Production notes

  • Process records arrays asynchronously and acknowledge immediately.
  • Choose whether failed webhook actions should let a contact continue or exit the journey.
  • Autopilot and current Ortto screens use different product terminology.

Related documentation