workflows-and-webhooks

Workflows & Webhooks

Workflows and Webhooks provide powerful automation and integration capabilities — letting you build multi-step automated processes and connect Ariadne to external systems.

Workflows

What Are Workflows?

Workflows are automated sequences of steps that Ariadne can execute. They allow you to build structured automation pipelines — for example, a workflow that receives data, processes it with an agent, and sends the result somewhere.

Accessing Workflows

Go to Settings → Workflows in the top navigation.

Creating a Workflow

1. Click New Workflow
2. Define the workflow steps — each step can:
   • Call an agent with a specific prompt
   • Transform data
   • Route to different branches based on conditions
   • Call external services
3. Define the trigger — how the workflow starts (manual, scheduled, or webhook-triggered)
4. Click Save

Running a Workflow Manually

From the Workflows page, click Run next to any workflow to execute it immediately. You can view the execution log and results.

Workflow Triggers

Workflows can be triggered in multiple ways:

• Manual – run from the UI on demand
• Scheduled – combine with a schedule (see Goals & Schedules)
• Webhook – triggered by an external HTTP request (see Webhooks below)

Webhooks

What Are Webhooks?

Webhooks are HTTP endpoints that external systems can call to trigger actions in Ariadne. When an external system (a CI/CD pipeline, a form submission service, a monitoring tool, etc.) sends an HTTP request to your webhook URL, Ariadne can react to it — for example, by starting an agent conversation or executing a workflow.

Accessing Webhooks

Go to Settings → Webhooks in the top navigation.

Creating a Webhook

1. Click New Webhook
2. Enter:
   • Name – a descriptive label
   • Agent / Conversation – where to route incoming events
   • Prompt template – the message to send to the agent when triggered (can include variables from the incoming request payload)
3. Click Save
4. Copy the generated Webhook URL — this is the URL you'll configure in the external system

Webhook URL Format

https://your-ariadne-instance.com/api/webhook/{webhookId}

Send a POST request to this URL from any system. The request body (JSON) is available as variables in the prompt template.

Example: CI/CD Notification

Configure your CI/CD pipeline to call your webhook when a deployment completes. Your prompt template might be:

"A deployment has completed: {{status}} for service {{service}} at {{timestamp}}. Review the deployment and update the project work board accordingly."

When the webhook fires, the agent receives the populated prompt and takes action.

Securing Webhooks

Each webhook URL is unique and unpredictable, providing basic security through obscurity. For additional security:

• Treat the webhook URL as a secret — don't expose it publicly
• Consider adding IP allowlisting at the network level if your infrastructure supports it

Managing Webhooks

• Disable a webhook without deleting it
• View logs of recent webhook calls and their outcomes
• Regenerate URL to invalidate the old URL if it has been compromised
• Delete when no longer needed

Use Cases