​

Output Routes

​

Concepts

​

Events

​

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

​

Scoping Deliveries

​

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

​

Configuration

​

Signature Verification

X-CrewForm-Signature: sha256=<hex-signature>

// 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

​

Setup

1. Go to api.slack.com/apps → Create 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

​

Message Format

✅ 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

​

Setup

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

​

Configuration

​

Message Format

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

​

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

​

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

​

Setup

1. In Teams, open the channel → Connectors (⋯ menu → Connectors)
2. Find Incoming Webhook → Configure
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

​

Message Format

• 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

​

Setup

1. Go to app.asana.com/0/my-apps → Create 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

​

Task Format

• 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

​

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

​

Card Format

• Name: [CrewForm] <task title> — <status>
• Description: Event type, task/agent details, timestamp, and full result

​

Bidirectional Flow

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

​

Self-Hosted Environment Variables

​

Notion

​

Setup

1. Go to notion.so/my-integrations → New Integration
2. Give it a name (e.g. “CrewForm”) and select your workspace
3. Copy the Internal Integration Token (starts with ntn_...)
4. In Notion, open the target database → ⋯ → Connections → Add connection → select your integration

​

Configuration

​

Page Format

• Title: [CrewForm] <task title> — <status>
• Content: Event type, agent details, timestamp, and full result as text blocks

​

GitHub Issues

​

Setup

1. Go to github.com/settings/tokens → Generate new token (classic)
2. Select the repo scope
3. Copy the Personal Access Token

​

Configuration

​

Issue Format

• Title: [CrewForm] <task title> — <status>
• Body: Event type, agent details, timestamp, and full result in Markdown

​

Email (Resend)

​

Setup

1. Sign up at resend.com and verify a sending domain
2. Go to API Keys → create a new key
3. Copy the API Key

​

Configuration

​

SMTP Email

​

Configuration

Gmail SMTP: Use an App Password (not your regular password). Go to Google Account → Security → 2-Step Verification → App passwords.

​

Linear

​

Setup

1. Go to linear.app/settings/api → Personal API keys → create a key
2. Copy the API Key
3. Find your Team Key (the short prefix like ENG, OPS visible in issue IDs)

​

Configuration

​

Issue Format

• Title: [CrewForm] <task title> — <status>
• Description: Full result in Markdown with agent and event metadata

​

Google Workspace

​

Setup (One-Time)

1. When creating a Google output route, click Connect Google in the configuration form
2. Sign in with your Google account and grant the requested permissions
3. CrewForm stores encrypted OAuth tokens — no API keys needed

Self-Hosted: You must configure a Google Cloud project with OAuth credentials. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET on both Supabase Edge Functions and the task runner. See the Self-Hosting Guide for details.

​

Google Sheets

​

Gmail

​

Google Docs

​

Google Calendar