flowcastle.ai

List the applications this API key can access, with the caller role and the permissions it grants.

Create a new application (workspace) owned by the caller.

Update application-level settings (name, active state, default language, incoming-message behavior).

List the group/channel chats a telegram_mtproto userbot monitors.

Replace a telegram_mtproto userbot's watched-groups list — the chats it monitors.

Import a telegram_mtproto userbot's existing chats as contacts — DM partners, groups, and channels — so everything the account already talks to becomes a valid send_message target without waiting for each chat to message first.

Return a compact application, flow, sequence, operation, and bot summary — the cheapest way to orient in a workspace.

Search variable definitions by scope and keyword.

Return the full application-level automation context in one read-only call: every flow (with folders), connected bots, variables, sequences, and operations.

Return a compact index of both installed and available marketplace modules, with each module's key, versions, description, actions, and triggers.

Return everything needed to use one module: action input fields and their types, trigger configuration, manual setup fields (credentials an operator must fill in the dashboard), and references to already-installed actions.

Install an exact marketplace module version into an application and create any missing installed-template actions.

Return one flow's graph topology: its blocks, how they link, and a short summary per block.

Return the complete contents of one block: block data, action configs, HTTP request bodies, custom-code files, triggers, menu payloads, and media paths.

Return the action-authoring contract: every supported action kind with its required fields, the placeholder ids for referencing entities created earlier in the same batch, the `{{var|.

Return the flow-design rules that validation does NOT enforce: when to split a branch into its own flow, how navigation and menus must be wired, and worked examples.

Search the library of reusable flow examples covering common business cases (lead capture, onboarding, payments, reminders).

Return one reusable flow example by id, optionally with a complete action batch you can adapt and pass to apply_actions.

Dry-run validation of a proposed batch of flow-builder actions.

Validate and apply a batch of flow-builder actions — the single write path for editing flows, blocks, variables, broadcasts, sequences, and folders.

Runs deterministic behavioural tests against flows that are ALREADY applied (compiles them to an AST and simulates a user).

Send a message to ONE contact right now, outside any flow.

List and search contacts in the application, paginated, newest first.

Return one contact's full profile plus every contact-variable value stored for them.

Return one contact's engagement history: goals they achieved and buttons they clicked, newest first, plus all-time goal totals.

The reverse lookup: which contacts triggered one analytics event — achieved a goal (kind GOAL + goalKey), clicked a button (BUTTON_CLICK + blockId, optionally buttonId/buttonIndex), were sent a block (BLOCK_SENT + blockId), or received a broadcast (BROADCAST_DELIVERED + broadcastId).

Create a contact manually — for imports or externally-sourced audiences; contacts who message a bot are created automatically.

Update a contact's profile fields and/or contact-variable values.

List broadcasts in the application with status, schedule, and delivery counts.

Return full details for a single broadcast: status, schedule, recurrence rule, linked flow, and delivery breakdown by status.

Return engagement analytics for a broadcast: delivery breakdown by status plus per-message-block sent and clicked counts for its flow, over an optional date window.