Chatigram

View saved version →

---
name: chatigram-workflows
description: Use Chatigram to build and manage automations across schedules, webhooks, API requests, database changes and customer messages. Create and edit workflows, connect supported services, manage records and review changes before saving.
---

# Chatigram automations

Use the connected Chatigram tools to perform the user's authorized task. Resolve the organization through list_organizations, following pagination, and pass its ID on every scoped call. If several names match, ask which one. Check organization_capabilities for the current Admin role, permissions and plan limits. Do not bypass a denied operation or use another organization as a substitute.

Only members with the Admin role in the selected organization may use the plugin for that organization. Authorization is rechecked on scoped operations and queued event delivery; an existing connection does not preserve access after role loss.

## Build and manage workflows

Find existing workflows with list_workflows and read_workflow. Discover actual triggers, nodes, configuration fields, connections and templates through the tools; do not invent capabilities. Workflows can use schedules, webhooks, HTTP endpoints, database changes or conversation events. Check the trigger's context against the nodes' requirements.

Use an owned draft, make the requested changes, then preview_draft. Show a concise summary of the changes, paths and unresolved setup before saving. Respect preview-only, disabled and unassigned requests. A request can authorize creation, saving, assignment and activation together; do not add redundant confirmations. Activate, execute, assign or send only within the user's explicit task scope. Keep unrelated resources and protected account bindings unchanged.

Follow [workflow authoring](references/authoring.md) for drafts, triggers, expressions and Properties. Follow [resource operations](references/operations.md) for databases, records, Lines, Inbox and connections.

## Confirm structural deletion separately

An initial request to delete a database, table, whole workflow or Line authorizes inspection and a deletion preview only. Show the exact organization, resource type, name, ID and irreversible consequences. End the response and wait for separate explicit confirmation in a later user message before committing that reviewed deletion. If the target, impact or preview changes, show a fresh preview and obtain a new confirmation.

Discover the supported deletion tool first. If database or whole-workflow deletion is unavailable, explain that limit; do not simulate it by deleting children. This extra confirmation does not apply to creation, ordinary edits or record operations within previously authorized automations. Existing permissions and other operation-specific safeguards still apply.

## Approve paid processing before use

Before first adding, binding or invoking a paid capability, explain the actual service, selected account/connection, transferred content and intended spending scope, and obtain explicit approval. This includes indirect calls through nodes, HTTP requests, integrations and other workflows. General workflow authorization is not spending approval. Normal saved operation within the approved scope does not require repeated approval unless that scope changes.

Apply spending approval to direct and indirect operations, including workflow runs. Identify the selected service and transferred content when obtaining consent; do not disclose credentials or unrelated implementation details.

## Handle events and Tasks

Follow [events and ChatGPT Tasks](references/events-and-tasks.md) for user-authorized monitoring and optional asynchronous task handling. Connecting the plugin does not create subscriptions. ChatGPT Task workflows require real delivery readiness and explicit Error and Timeout paths.

## Protect data and report actual results

Credentials belong only in authenticated Chatigram setup forms. Never ask for or r

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.