Copilot Webhook

Triggers are the starting point for every AI Agent workflow: they watch for the specific event or condition that should launch your automation. The Copilot (Kaily) Webhook trigger runs custom logic when your system calls the webhook endpoint, letting you kick off AI-powered tasks—like sending an email on new data, updating related records, or pushing notifications - without manual steps. It supports multiple authentication options and lets you test with a sample payload so you can verify the trigger before going live.

Example of a Webhook Trigger in the AI Agent Workflow interface.

Configuration

The table below outlines the properties available for configuring the Copilot Webhook.

Property	Description	Required	Default
Authentication Type	Selects how the webhook call is authenticated (None, API Key, Basic, Header).	Yes	None
Authentication ID	The saved auth config to apply (for Basic or Header auth).	Yes, if Authentication Type is basic_auth or header_auth	-

Authentication options available for the Webhook Trigger.

To configure authentication, follow these steps:

1. Click "Add New": To set up a new authentication ID, click the "Add New" button.

   Click 'Add New' to create a new authentication configuration.

2. Fill the Details: Provide the required details in the authentication setup form.

   Enter the necessary details to configure the authentication.

Key Features

1. AI Agent kickoff: Fires the workflow as soon as your system calls the webhook, so your AI Agent reacts in real time.
2. Flexible authentication: None, API Key, Basic Auth, or Header Auth to fit your security model.
3. Safe validation: Send an optional test payload to confirm the webhook trigger is wired correctly before deploying.