Automations
AutomationsAmbiguous Automations. Trigger, filter, and action workflows connecting webhooks, events, and the Assistant.
Connect events across your workspace with simple trigger, filter, and action recipes. When a customer emails support, automatically create a CRM ticket. When a deal closes, notify the team in Chat. For steps that need judgment, hand off to the Assistant mid-workflow.
Features
A visual recipe builder. Pick a trigger (form submitted, email received, task completed), add filters (subject contains, deal value above), choose an action (create task, send email, ask the Assistant). Recipes run in the background, no code required.
Recipe builder
Drag-and-drop canvas with trigger, filter, and action nodes. Connect them in sequence or branch on conditions.
Included from day one
The rest of the Automations feature set. Every item ships in every workspace, for your team and your AI coworkers alike.
Trigger catalog
Internal events (mail received, form submitted, task completed, deal stage changed) and external webhooks from any service.
Filter editor
Narrow which events fire the action. Filter on field values, sender, labels, deal size, or custom conditions.
Action picker
Send an email, create a task, update a CRM deal, post in Chat, or hand off to the Assistant for open-ended judgment.
Run history
Every execution logged with trigger payload, filter result, and action outcome. Debug failed runs in one click.
Webhook endpoints
Each recipe gets a unique webhook URL. Point any external service at it to trigger your workflow.
Triggers your automations can listen on
Every event in the workspace is available as a trigger. Combine with filters to narrow which events fire your workflow.
mail.received
Fires when a new email arrives in any inbox on the workspace domain.
form.submitted
Fires when a public form receives a response.
task.completed
Fires when any task is marked complete by a human or coworker.
deal.stageChanged
Fires when a CRM deal moves to a new pipeline stage.
calendar.eventCreated
Fires when a new meeting or event is added to any calendar.
webhook.received
Fires when an external service posts to your recipe's unique webhook URL.
One product, two ways in
Your agent creates automations, registers webhooks, and queries run history via MCP. Build event-driven workflows that react to external signals without polling. Pair with Mail and CRM tools for inbound-lead qualification pipelines.
// Create an automation that triages inbound mail
const automation = await mcp.callTool("automations.create", {
name: "Triage inbound mail",
trigger: { type: "mail.received", filter: { label: "support" } },
action: {
type: "assistant.run",
prompt: "Classify and respond to this email."
}
});curl -X POST https://app.ambi.cc/api/webhooks \
-H "Authorization: Bearer $AMBIGUOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-agent.example.com/hooks/automations",
"events": [
"mail.received",
"form.submitted",
"task.completed",
"deal.stageChanged"
],
"secret": "whsec_your_signing_secret"
}'// Query available event types for automation triggers
const events = await mcp.callTool("automations.listNodeTypes", {
type: "trigger"
});
// Returns: mail.received, form.submitted, task.completed,
// deal.stageChanged, calendar.eventCreated, webhook.receivedWhat your agent can do in Automations
Every action your team takes in Automations, your agent can do the same way.
| Method | Description |
|---|---|
| automations.create | Create a trigger, filter, action workflow |
| automations.list | List all automations with status and run counts |
| automations.run | Manually trigger an automation with sample data |
| automations.enable | Enable a paused automation |
| automations.disable | Pause an active automation |
| automations.listRuns | View execution history with success/failure status |
| webhooks.create | Register a webhook endpoint for workspace events |
| webhooks.listEventTypes | List all available webhook event types |
Automations can hand off to the Assistant
Most workflow engines stop at deterministic steps. Route any step to an AI judgment call: classify an inbound email, draft a response based on context, decide whether a lead qualifies. The trigger fires, the filter narrows, and the Assistant handles it.
