Choose a trigger
Compare conversation, schedule, database, manual, webhook, and HTTP triggers, and choose the event your workflow really needs.
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Active workflows | 3 | 10 | 45 | Unlimited |
Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.
Match the event to the task #
This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.
| Trigger | Starts when | Good for |
|---|---|---|
| New Chat Created | The first message arrives for a fresh chat | A one-time welcome |
| Conversation Start | The configured new-chat or target-message condition matches | An entry point or restart command |
| New Text Message | An incoming text-message event occurs | Text-driven automation |
| Chat Status Change | The configured conversation status changes | Follow-up or handoff flows |
| Manual | You click Run on the workflow page | A deliberate business task or controlled test |
| Cron | The configured schedule becomes due | Repeated checks and scheduled tasks |
| Database Operation | A selected table receives a selected row operation | Reacting to a created, updated, or deleted record |
| Webhook | A request reaches the configured webhook | Receiving events from another service |
| HTTP Endpoint | A request reaches the workflow endpoint | Request-driven work with an optional custom response |
Conversation triggers #
Conversation triggers provide context for actions such as sending a reply or changing a conversation status. Make sure the workflow is enabled and eligible for the Line receiving the event.
New Chat Created is not the same as every new message. Conversation Start can match configured target messages; at least one start condition must be enabled. Test the exact event you configured.
Avoid two overlapping triggers that both answer the same customer message unless that is deliberate.
Manual workflows #
Use Run for a saved, enabled Manual workflow. Manual runs do not create an artificial customer conversation. Use nodes that work with their own configured inputs and resources.
The manual starter recipe is a small copyable example without an external account requirement.
Schedules #
Cron supports simple schedule controls and an advanced expression mode. Set the timezone explicitly. A daily time in one timezone is not the same instant as that time in another, and daylight-saving changes can affect local schedules.
Start with the schedule guide and check the next real run in Workflow Activity.
Database operations #
Select the database, table, and at least one row operation. Update events can expose changed fields and previous/next values. If the workflow writes to the same watched table, add a condition that prevents it from repeatedly triggering itself.
Database availability follows your plan. See database workflows.
Webhook or HTTP Endpoint? #
Use a Webhook for receiving an event. Use HTTP Endpoint when the calling application needs the workflow’s supported HTTP response behavior. Add HTTP Response if you need a custom response; without one, a completed synchronous endpoint can return 204 No Content.
Workflows that wait for a ChatGPT Task can return an acknowledgement while the task remains pending. A later completion does not replace an HTTP response already sent. See HTTP requests and endpoints.