Workflow Automation
A workflow is an automation that runs on Indite's servers — no chat window needed. It starts from a trigger (a schedule, a webhook, a WhatsApp message, a new email…) and then runs a chain of blocks: AI agents, integrations, data transforms, and logic.
Build it visually by dragging blocks onto a canvas — or just describe it to Indite Copilot and let AI build it for you.
What you can automate
- Reply to customers on WhatsApp, Telegram, Slack, or Instagram with AI-generated answers grounded in your knowledge base
- Process email — read incoming Gmail/Outlook messages, summarize, route, and reply automatically
- Sync data between sheets, databases, and CRMs on a schedule
- React to payments — Stripe or Razorpay events trigger invoices, notifications, and fulfilment
- Run AI agents that reason in steps, search the web, query your database, and call any API or MCP server
The building blocks
The workflow editor gives you 160+ blocks in 7 categories:
| Category | What it gives you |
|---|---|
| 26 Triggers | Manual, Schedule, Webhook, WhatsApp, Gmail, Slack, Stripe, Supabase, HubSpot, Jira, and more |
| 19 Actions | HTTP Request, Send Email, LLM Agent, Guardrails, file & data helpers |
| 95 Integrations | One block per app — each with its own menu of operations |
| 5 Models | OpenAI, Claude, Gemini, Groq, AWS Bedrock |
| 5 Tools | Web search, MCP servers, SQL, API, and custom-code tools for your agents |
| 12 Databases | SQL, NoSQL, Google Sheets, Airtable, Supabase, vector stores |
| 7 Logic blocks | Condition, Switch, For Each, Wait, Set Variable, Script, Human In The Loop |
How a workflow lifecycle works
- Build — add a trigger and connect blocks on the canvas. A workflow can have multiple triggers, each starting its own branch.
- Test — run individual blocks or the whole flow, and inspect each block's output.
- Publish — click Publish in the header. Editing a published workflow unpublishes it first.
- Activate — workflows with automatic triggers (schedule, webhook, messaging…) get an Active/Inactive switch. Manual workflows run from the play button on their trigger.
- Monitor — the Executions page shows every run with a step-by-step timeline, and History keeps versions you can restore.
Data moves between blocks through variables and block outputs — reference any previous block's result with {{blockId.field}} style mappings, configured in each block's Save answer section.