Source type

Autopilot Journeys Source Configuration

Autopilot Journeys and Ortto sources receive journey webhook actions, batched contact records, and custom activity streams.

AUTOPILOTPOSTAuthorization SecretEmail and messaging
Autopilot webhook action documentationAll source types
Autopilot Journeys / Ortto sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.Autopilot Journeys / OrttoProviderPOSTSignedFastHookSource URLAUTOPILOTProvider credentialheader authVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Autopilot Journeys configuration

Create a Autopilot Journeys source, keep POST enabled, and provide the configured Authorization Secret values for provider signature. FastHook uses these settings to validate each Autopilot Journeys / Ortto delivery before it enters the routing workflow.

Source Type

AUTOPILOT

Allowed methods

POST

Authentication

Provider signature

Credential fields

Authorization Secret

Autopilot Journeys source config
{
  "type": "AUTOPILOT",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "AUTOPILOT",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST"]
  }
}

Autopilot Journeys request contract

FastHook compares the configured Authorization value before accepting the journey payload.

POST

Autopilot Journeys / Ortto headers

Preserve Authorization when sending Autopilot Journeys / Ortto test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Authorization

Pre-shared secret or Bearer value configured on the webhook action.

Autopilot Journeys / Ortto setup

  1. Create an Autopilot or Ortto webhook action at the required journey step.
  2. Use the FastHook Source URL and add Authorization: Bearer YOUR_SECRET as a custom header.
  3. Allow for batched records arrays containing multiple contacts.
  4. Acknowledge quickly because the legacy action waits five seconds and retries only twice.

Continue with Autopilot Journeys