Overview
The third-party connector lets you send data from Go Autonomous to any external system at defined points during request processing. You configure one or more webhook actions — each pairing a lifecycle event (such as “On Confirmation”) with a target URL — so Go Autonomous calls your system automatically as requests move through the pipeline. Multiple third-party connectors can be created, one for each external system you need to connect to.You must have at least one Authenticator configured before you can create a third-party connector. The connector uses the authenticator to handle credentials for all its outbound calls.
Configuration fields
| Field | Description |
|---|---|
| Name | A label for the connector — used to identify it in the connectors list. |
| Authenticator | The authenticator that provides credentials for all webhook calls made by this connector. Required. |
| Webhook base URL | The base URL (e.g. https://your-base-url.com) that’s prepended to any webhook endpoints entered as a relative path. Required when at least one webhook uses a relative endpoint; otherwise optional. |
| Webhook configurations | One or more webhook actions defining when and where Go Autonomous sends data (see below). At least one is required. |
Webhook actions
Each webhook configuration pairs a lifecycle event (the event trigger) with a target URL. When the event occurs on a request, Go Autonomous posts data to that URL.Webhook URLs: absolute vs. relative
Webhook URLs can be entered in either format:- Absolute URL — e.g.
https://your-system.com/hooks/confirmation. Used as-is. - Relative path — e.g.
/hooks/confirmation. Appended to the connector’s Webhook base URL at delivery time.
Available event triggers
| Event | When it fires |
|---|---|
| On Classification | After Go Autonomous classifies the intent of an incoming request. |
| On Extraction | After AI extraction has run and fields have been populated. |
| On Account Resolution | After the customer account has been resolved against your data. |
| On Transformation | After any transformation steps have been applied to the request data. |
| On Confirmation | When a request is confirmed in Flow. |
| On Field Update | When a specific field value is updated on a request (see below). |
On Field Update
The On Field Update event fires whenever a specific field is changed. When you select this event trigger, an additional Field picker appears — choose the exact field (from your configured field settings) that should trigger the webhook. You can add multiple On Field Update rows, each watching a different field. Each field can only be used once per connector.Set up a third-party connector
Select an authenticator
Choose the authenticator that holds the credentials for your target system. If none exist yet, you’ll be prompted to create one first.
Set the webhook base URL (optional)
If your webhooks share a host, enter it under Webhook base URL (e.g.
https://your-system.com). You can then enter each webhook below as a relative path. Leave this blank if you’ll enter full absolute URLs for every webhook.Configure webhook actions
Add one or more webhook rows. For each row:
- Select the event trigger that should fire the call.
- Enter the webhook URL — either a full absolute URL or a relative path (e.g.
/hooks/confirmation) that will be appended to the base URL. - If using On Field Update, also select the field to watch.
Managing webhook rows
- Add a row — click the add button below the webhook list to add another event/URL pair.
- Delete a row — click the delete icon on any row. You cannot delete the last remaining row; at least one webhook configuration must always be present.
Integration events
After the connector is active, use the Integration Events feed to monitor its health. It shows a log of recent outbound calls, including:- Successful deliveries.
- Errors and failed calls.
- Timestamps and payload details for troubleshooting.
What’s next
- Configure authenticators to manage the credentials used by your connectors.
- Connectors overview for other available connector types.