Database triggers and event monitoring
Choose workflow triggers, REST API webhooks, or supported AI event subscriptions to react when Chatigram database records change.
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Databases | Not included | 1 | 2 | Unlimited |
| 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.
Choose where the reaction runs #
| Approach | Best for | Setup |
|---|---|---|
| Database Operation workflow trigger | Automations inside Chatigram | Choose the database, table, and operations in a workflow |
| Database API webhook | Notifying your external application | Enable the database API and follow its OpenAPI specification |
| AI connection event subscription | Monitoring through a host that supports Chatigram events | Explicitly request the database, table, event, and permitted response |
These are separate configurations. Adding a workflow trigger does not establish an AI subscription or an external API webhook.
Start a Chatigram workflow #
Use Database Operation for created, updated, or deleted rows. For example, when a new request is created, validate its fields, send an internal notification, and update its status.
For updates, inspect the changed fields before taking action. A workflow that writes back to its watched table needs a condition that prevents repeated self-triggering. See database workflow operations and the database-change recipe.
Notify external software #
The database REST API supports webhook subscriptions for CREATE, UPDATE, and DELETE. Use your downloaded specification for the subscription request and payloads. The receiver must use HTTPS.
A database has at most one API webhook subscription. Subscribing again replaces the destination, selected operations, and signing secret. Coordinate changes with anyone already using that subscription.
Delivered event names are row.created, row.updated, and row.deleted. Updates include the row before and after the change; create and delete events include the relevant row data. Store the returned signing secret securely and verify deliveries using the documented signature before processing them. Design the receiver to handle duplicate deliveries without repeating business actions.
Monitor through an AI connection #
The public ChatGPT plugin listing is under review. These prompts are for workspaces where the Chatigram plugin is available and connected. Status reviewed 2026-11-10.
Where the host supports event subscriptions, the Chatigram connection exposes database.record.created, database.record.updated, and database.record.deleted for a selected database and table. Connecting your account alone does not start monitoring.
Copy and customize this request:
In Chatigram, find my [organization], the [Customer requests] database,
and its [Requests] table. Check whether this connection supports database
record-created event subscriptions. If supported, monitor new records
and summarize the request when an event arrives. Do not send messages,
edit records, or activate workflows. Confirm what is subscribed and
report any subscription expiry or delivery limitations.
The host manages the callback setup; you do not need to paste keys or callback credentials into chat. Subscriptions can expire or stop when authorization changes. Ask to check subscription status, and explicitly request cancellation when monitoring is no longer needed. Host support and availability must be checked at the time of setup.