Documentation Index

Fetch the complete documentation index at: https://docs.crewform.tech/llms.txt

Use this file to discover all available pages before exploring further.

​

Channels (Inbound Messaging)

​

How Channels Work

User sends message
       │
       ▼
Platform webhook → CrewForm Edge Function
       │
       ▼
Task / Team Run created (status: dispatched)
       │
       ▼
Task Runner picks up → Agent executes
       │
       ▼
Result sent back to originating chat

​

Managed Bot vs Bring Your Own Bot (BYOB)

​

Managed Bot

​

Bring Your Own Bot (BYOB)

​

Telegram

​

Managed Bot Setup

1. Create the channel in CrewForm:
   • Go to Settings → Channels → New Channel → Telegram
   • Toggle Managed Bot ON
   • Set a Default Agent or Default Team
   • Save — a connect code is generated
2. Link your Telegram chat:
   • Open the chat, group, or channel in Telegram
   • Send: /connect <your_connect_code>
   • The bot replies: ✅ Connected! Messages in this chat will be routed to your configured agent.
3. Send tasks:
   • Any text message is routed to the agent
   • Or use /ask <prompt> to be explicit

​

BYOB Setup

1. Create a bot via @BotFather → /newbot → copy the Bot Token
2. In CrewForm: Settings → Channels → New Channel → Telegram
3. Toggle Managed Bot OFF
4. Paste the Bot Token and your Chat ID
5. Set the Webhook URL on your bot:
   curl -X POST "https://api.telegram.org/bot<TOKEN>/setWebhook" \
     -d "url=https://<your-supabase-project>.supabase.co/functions/v1/channel-telegram"
   

​

How Messages Are Handled

​

Required Environment Variables (Self-Hosted)

​

Slack

​

Managed Bot Setup

1. Create the channel in CrewForm:
   • Go to Settings → Channels → New Channel → Slack
   • Toggle Managed Bot ON
   • Set a Default Agent or Default Team
   • Save — a connect code is generated
2. Invite the bot to your Slack channel:
   • In Slack, type /invite @CrewForm in the target channel
3. Link the Slack channel:
   • In the Slack channel, send: connect <your_connect_code>
   • The bot replies: ✅ Connected! Messages in this channel will now be routed to your configured agent.
4. Send tasks:
   • Any message in the channel is routed to the agent

​

BYOB Setup

1. Create a Slack app at api.slack.com/apps
2. Enable Event Subscriptions and add message.channels (or message.groups for private channels) under Subscribe to bot events
3. Set the Request URL to:
   https://<your-supabase-project>.supabase.co/functions/v1/channel-slack
   
   Slack will send a url_verification challenge — CrewForm responds to it automatically.
4. Go to OAuth & Permissions → add scopes: chat:write, reactions:add, channels:history
5. Install the app to your workspace and copy the Bot User OAuth Token (xoxb-...)
6. In CrewForm: Settings → Channels → New Channel → Slack
   • Toggle Managed Bot OFF
   • Paste the Bot Token and Channel ID

​

How Messages Are Handled

​

Required Environment Variables (Self-Hosted)

​

Discord

• Managed bot flow (invite → connect code → /connect → /ask)
• BYOB flow (custom Discord app, Ed25519 signature verification, slash command registration)
• Deferred responses and the “thinking…” indicator
• Troubleshooting

​

Required Environment Variables (Self-Hosted)

​

Email

​

How It Works

1. Emails arrive at a dedicated inbound address (e.g. agent@mail.yourapp.com)
2. Resend receives the email and fires an email.received webhook to CrewForm
3. CrewForm fetches the email body via the Resend API, creates a task, and runs the agent
4. The agent’s result is sent back as a reply email to the original sender

​

Setup

​

1. Configure Resend Inbound

1. Sign up at resend.com and add your domain
2. Add an MX record to your domain DNS:
   Type: MX
   Name: mail  (or your inbound subdomain)
   Value: inbound-smtp.us-east-1.resend.com
   Priority: 10
   TTL: 300
   
   This routes emails sent to @mail.yourdomain.com through Resend.
3. In the Resend dashboard → Inbound → Add Webhook:
   • Event: email.received
   • URL:
     https://<your-supabase-project>.supabase.co/functions/v1/channel-email
     

​

2. Create the Channel in CrewForm

1. Go to Settings → Channels → New Channel → Email
2. Set the Inbound Address — the full email address or prefix that should trigger this channel (e.g. agent@mail.yourdomain.com)
3. Set a Default Agent or Default Team
4. Save

​

3. Configure Reply Sending

​

How Emails Are Processed

Attachments: Email attachments are not currently included in the agent prompt. Only the subject and body are used.

​

Reply Format

• From: RESEND_FROM_ADDRESS
• To: Original sender
• Subject: Re: <original subject>
• Body: Agent result in a styled HTML block

​

Routing Multiple Agents

​

Required Environment Variables (Self-Hosted)

​

Trello

​

Setup

​

1. Get Trello API Credentials

1. Go to trello.com/power-ups/admin
2. Create or select a Power-Up to get your API Key
3. From the API key page, click the Token link to generate a token with read/write access

​

2. Find Your Board and List IDs

1. Board ID — open the board in Trello; the short ID is in the URL: https://trello.com/b/<BOARD_ID>/...
2. List IDs — use the Trello API:
   curl "https://api.trello.com/1/boards/<BOARD_ID>/lists?key=<KEY>&token=<TOKEN>"
   
   You’ll need:
   • Trigger List ID — cards created or moved here start agent tasks
   • Review List ID (optional) — completed cards are moved here after results are posted

​

3. Create the Channel in CrewForm

1. Go to Settings → Channels → New Channel → Trello
2. Enter your API Key, Token, Board ID, Trigger List ID, and optionally a Review List ID
3. Set a Default Agent or Default Team
4. Save — CrewForm registers a webhook on the board automatically via the trello-webhook-register Edge Function

​

How Cards Are Handled

1. The result is posted as a comment on the original Trello card
2. If a Review List is configured, the card is moved there
3. A trello_card_mappings record links the Trello card to the CrewForm task

​

Bidirectional Flow with Output Routes

Card moved to "AI Work" list
       │
       ▼
CrewForm creates task + card mapping
       │
       ▼
Agent processes the prompt
       │
       ▼
Result posted as comment on card
       │
       ▼
Card moved to "Review" list

Tip: Create two lists on your board — “AI Work” (trigger) and “Review” (review) — for a clean Kanban workflow with your AI agents.

​

Webhook Management

# Register
curl -X POST "https://<your-project>.supabase.co/functions/v1/trello-webhook-register" \
  -H "Authorization: Bearer <supabase-anon-key>" \
  -H "Content-Type: application/json" \
  -d '{"action": "register", "channelId": "<channel-uuid>"}'

# Unregister
curl -X POST "https://<your-project>.supabase.co/functions/v1/trello-webhook-register" \
  -H "Authorization: Bearer <supabase-anon-key>" \
  -H "Content-Type: application/json" \
  -d '{"action": "unregister", "channelId": "<channel-uuid>"}'

​

Required Environment Variables (Self-Hosted)

​

Linear

​

Setup

​

1. Get a Linear Personal API Key

1. Go to linear.app/settings/api
2. Click Create key → give it a label (e.g. “CrewForm”)
3. Copy the key (lin_api_...)

​

2. Find Your Team ID

1. In Linear, go to Settings → Teams → [Your Team]
2. The Team ID (UUID) is visible in the URL: https://linear.app/<workspace>/settings/teams/<TEAM_ID>

​

3. Create the Channel in CrewForm

1. Go to Settings → Channels → New Channel → Linear
2. Enter your Personal API Key and Team ID
3. Configure triggers:
   • Trigger On — comma-separated list: create, state_change, label
   • Trigger States (optional) — comma-separated state names, e.g. Triage,Todo
   • Trigger Labels (optional) — comma-separated label names, e.g. crewform,ai-task
   • Done State (optional) — move the issue to this state when the agent completes (e.g. Done)
4. Set a Default Agent or Default Team
5. Save — CrewForm automatically registers a webhook on your Linear team via the linear-webhook-register Edge Function

​

Trigger Configuration

Tip: Use state_change or label triggers to avoid processing every new issue. For example, label issues with “ai-task” to selectively trigger your agent.

​

How Issues Are Handled

1. The result is posted as a comment on the original Linear issue
2. If a Done State is configured, the issue is moved to that state
3. A linear_issue_mappings record links the Linear issue to the CrewForm task

​

Bidirectional Flow

Issue created / state changed / label added
       │
       ▼
CrewForm creates task + issue mapping
       │
       ▼
Agent processes the prompt (issue description)
       │
       ▼
Result posted as comment on issue
       │
       ▼
Issue moved to "Done" state (optional)

​

Priority Mapping

​

Webhook Management

# List webhooks
curl -X POST https://api.linear.app/graphql \
  -H "Authorization: lin_api_..." \
  -H "Content-Type: application/json" \
  -d '{"query": "{ webhooks { nodes { id url enabled } } }"}'

​

Required Environment Variables (Self-Hosted)

​

Message Log

​

Choosing Managed Bot vs BYOB