Skip to main content

Output Routes

Output routes deliver agent and team run results to external destinations when a task completes or fails. Each route listens for specific events and posts a structured payload to its configured destination. Supported destinations:
TypeHow it delivers
HTTP WebhookPOST to any URL with HMAC-SHA256 signing
SlackIncoming Webhook — formatted message with result block
DiscordDiscord Webhook — embedded message with result
TelegramBot API — sends message to a chat or group
Microsoft TeamsIncoming Webhook — Adaptive Card
AsanaCreates a task in a project via Personal Access Token
TrelloCreates or updates a card on a board via API Key + Token

Concepts

Events

Every route subscribes to one or more events. Only matching events trigger delivery:
EventFires when
task.completedAn agent task finishes successfully
task.failedAn agent task errors out
team_run.completedA pipeline, orchestrator, or collaboration team run finishes
team_run.failedA team run errors out

Payload

Every route receives the same JSON payload:
{
  "event": "task.completed",
  "task_id": "uuid-or-null",
  "team_run_id": "uuid-or-null",
  "task_title": "Summarise Q4 earnings report",
  "agent_name": "Research Analyst",
  "status": "completed",
  "result_preview": "First 500 chars of the result...",
  "result_full": "Full result text...",
  "error": null,
  "timestamp": "2026-03-06T18:00:00.000Z",
  "attachments": [
    {
      "name": "report.pdf",
      "type": "application/pdf",
      "size": 204800,
      "url": "https://... (signed, expires in 24h)",
      "direction": "input"
    }
  ]
}
  • result_full — the complete output. Some destinations (Slack, Discord, Telegram, Teams) truncate long outputs in the formatted message; use HTTP if you need the full untruncated result.
  • attachments — file attachments associated with the task or team run. Signed download URLs expire after 24 hours.
  • task_id or team_run_id — only one will be set, depending on whether the event is from an agent task or a team run.

Retry

Each delivery is attempted up to 2 times (initial + 1 retry after 5 seconds). Failed deliveries are logged in Settings → Output Routes → Logs with the HTTP status code and error message.

Scoping Deliveries

By default, all active routes in a workspace receive all matching events. You can restrict an agent or team to only send to specific routes — see the Output Routes selector in Agents and Pipeline Teams.

Creating a Route

  1. Go to Settings → Output Routes
  2. Click New Route
  3. Choose the destination type and configure it
  4. Select which events to subscribe to
  5. Save — optionally test with the Send Test button

HTTP Webhook

The most flexible option. CrewForm POSTs the full JSON payload to your URL. Use this for custom integrations, internal tooling, or platforms not natively supported.

Configuration

FieldRequiredDescription
URLHTTPS endpoint to POST to
SecretOptionalIf set, CrewForm signs the payload with HMAC-SHA256

Signature Verification

If you set a secret, CrewForm adds a X-CrewForm-Signature header to every request:
X-CrewForm-Signature: sha256=<hex-signature>
The signature is computed as HMAC-SHA256(secret, raw-body). Verify it on your server:
// Node.js example
const crypto = require('crypto');

function verifyCrewFormSignature(rawBody, secret, signatureHeader) {
  const expected = 'sha256=' + crypto
    .createHmac('sha256', secret)
    .update(rawBody)
    .digest('hex');
  return crypto.timingSafeEqual(
    Buffer.from(signatureHeader),
    Buffer.from(expected)
  );
}
# Python example
import hmac, hashlib

def verify_signature(raw_body: bytes, secret: str, header: str) -> bool:
    expected = 'sha256=' + hmac.new(
        secret.encode(), raw_body, hashlib.sha256
    ).hexdigest()
    return hmac.compare_digest(expected, header)

Example Handler (Express)

app.post('/crewform-webhook', express.raw({ type: 'application/json' }), (req, res) => {
  const sig = req.headers['x-crewform-signature'];
  if (!verifyCrewFormSignature(req.body, process.env.CREWFORM_SECRET, sig)) {
    return res.status(401).send('Invalid signature');
  }

  const payload = JSON.parse(req.body);
  console.log(`Event: ${payload.event}, Task: ${payload.task_title}`);
  console.log(`Result: ${payload.result_full}`);

  res.sendStatus(200);
});
Tip: CrewForm treats any 2xx response as success. Return 200 quickly and process async to avoid timeouts.

Slack

Posts a formatted message to a Slack channel via an Incoming Webhook. Results appear in a coloured attachment block — green for completed, red for failed.

Setup

  1. Go to api.slack.com/appsCreate New App → From Scratch
  2. Go to Incoming Webhooks → Enable → Add New Webhook to Workspace
  3. Select the channel and click Allow
  4. Copy the Webhook URL (starts with https://hooks.slack.com/...)

Configuration

FieldRequiredDescription
Webhook URLSlack Incoming Webhook URL

Message Format

Messages are posted as Block Kit attachments:
✅ Task completed: Summarise Q4 earnings report
Agent: Research Analyst

```result output here```
Truncation: Results over 2,900 characters are truncated in the Slack message. Full output is always available in the HTTP webhook payload.

Discord

Posts an embedded message to a Discord channel via a Discord Webhook.

Setup

  1. In Discord, open the channel settings → Integrations → Webhooks
  2. Click New Webhook → give it a name
  3. Copy the Webhook URL

Configuration

FieldRequiredDescription
Webhook URLDiscord Webhook URL

Message Format

Results appear as Discord embeds — green border for completed, red for failed — with agent name, task title, status, and result inline.
Truncation: Results over 1,000 characters are truncated in the Discord embed. Use HTTP webhook if you need full output.
Note: This is a one-way output route (CrewForm → Discord). For two-way integration where Discord users can trigger agents via /ask, see the Discord Integration guide.

Telegram

Sends a message to a Telegram chat or group via the Bot API.

Setup

  1. Create a bot via @BotFather/newbot
  2. Copy the Bot Token (format: 123456789:AABBcc...)
  3. Get the Chat ID of the target chat:
    • For personal chats: message the bot, then visit https://api.telegram.org/bot<TOKEN>/getUpdates and find chat.id
    • For groups: add the bot to the group, send a message, check getUpdates
    • For channels: add the bot as admin, use the channel’s @username as the chat ID (e.g. @mycrewformchannel) or the numeric ID (e.g. -1001234567890)

Configuration

FieldRequiredDescription
Bot TokenToken from @BotFather
Chat IDNumeric chat ID, group ID, or @channelusername

Message Format

✅ Task completed

Title: Summarise Q4 earnings report
Agent: Research Analyst

```result output here```
Truncation: Results over 3,500 characters are truncated in the Telegram message.
Note: This is a one-way output route (CrewForm → Telegram). For two-way integration where Telegram users can trigger agents, see the Telegram Channel guide.

Microsoft Teams

Posts an Adaptive Card to a Teams channel via an Incoming Webhook. Cards render with a colour-coded header, fact set, and result body.

Setup

  1. In Teams, open the channel → Connectors (⋯ menu → Connectors)
  2. Find Incoming WebhookConfigure
  3. Give it a name and upload an icon (optional)
  4. Click Create and copy the Webhook URL
Modern Teams: Microsoft is migrating from Connectors to Workflows. If Connectors aren’t available in your tenant, use the Power Automate Workflows app instead: add the “Post to a channel when a webhook request is received” workflow and copy its URL.

Configuration

FieldRequiredDescription
Webhook URLTeams Incoming Webhook URL (or Power Automate Workflow URL)

Message Format

Delivered as an Adaptive Card (version 1.4):
  • Header: ✅ / ❌ with task/team run status
  • Fact Set: Prompt/Task, Agent/Team, Status
  • Body: Result text (monospace font)
  • Error: Shown if the task failed
Truncation: Results over 2,000 characters are truncated in the Teams card.

Asana

Creates a new task in an Asana project when a CrewForm task or team run completes or fails.

Setup

  1. Go to app.asana.com/0/my-appsCreate New Token (Personal Access Token)
  2. Copy the PAT
  3. Find your Project GID:
    • Open the project in Asana
    • The URL contains the GID: https://app.asana.com/0/<PROJECT_GID>/...
    • Or use the Asana API: GET https://app.asana.com/api/1.0/projects

Configuration

FieldRequiredDescription
Personal Access TokenAsana PAT from your account settings
Project GIDNumeric project ID from the Asana URL

Task Format

Each delivery creates an Asana task with:
  • Name: [CrewForm] <task title> — <status>
  • Notes: Event type, task/agent details, timestamp, and full result
Tip: Use Asana rules to automatically assign, tag, or move created tasks to specific sections based on their name or status.

Trello

Creates a new card (or updates an existing one) on a Trello board when a CrewForm task or team run completes or fails. Trello also supports bidirectional integration — cards moved to a trigger list can start agent tasks, and results are posted back as comments.

Setup

  1. Go to trello.com/power-ups/admin → create or select a Power-Up to get your API Key
  2. From the API key page, click the Token link to generate a token with read/write access
  3. Find your Board ID:
    • Open the board in Trello
    • The URL contains the ID: https://trello.com/b/<BOARD_ID>/...
  4. Find the List ID for the target list:
    • Use the Trello API: GET https://api.trello.com/1/boards/<BOARD_ID>/lists?key=<KEY>&token=<TOKEN>
    • Or use a browser extension like Trello Card Numbers
  5. (Optional) Find a Review List ID — completed cards will be moved here automatically

Configuration

FieldRequiredDescription
API KeyTrello API key from the Power-Up admin page
TokenTrello token with read/write access
Board IDBoard short ID from the Trello URL
Default List IDList where new result cards are created
Review List IDOptionalIf set, cards are moved here after results are posted

Card Format

Each delivery creates a Trello card with:
  • Name: [CrewForm] <task title> — <status>
  • Description: Event type, task/agent details, timestamp, and full result
If a card mapping already exists (from an inbound Trello trigger), the result is posted as a comment on the existing card instead of creating a new one, and the card is moved to the Review list.

Bidirectional Flow

When used with a Trello Messaging Channel, CrewForm supports a full round-trip:
  1. Inbound: A card is created or moved to the trigger list → CrewForm creates a task
  2. Agent processes the card’s title/description as the prompt
  3. Outbound: The agent result is posted as a comment on the original card → card moves to the Review list
Tip: Set up two lists on your board — an “AI Work” list (trigger) and a “Review” list (review) — for a clean Kanban workflow with your AI agents.

Delivery Logs

Every delivery attempt is logged. View logs in Settings → Output Routes → [Route Name] → Logs:
ColumnDescription
TimestampWhen delivery was attempted
EventWhich event triggered the delivery
Statussuccess or failed
HTTP CodeResponse code from the destination
ErrorError message if delivery failed
Logs are retained for 30 days.

Self-Hosted Environment Variables

If you self-host CrewForm, no extra environment variables are needed for output routes — all credentials are stored in the database per-route. The task runner reads them at delivery time. See the Self-Hosting Guide for general environment setup.