CLI Integration Commands

Integrations connect external services like Slack, Discord, Devin, and Cursor to your relay rules.

Supported providers: devin, cursor, slack, discord

List integrations

beeps integration list
beeps integration list --json

Get integration details

beeps integration get --integration-id int_abc123
beeps integration get --integration-id int_abc123 --json

Create an integration

The CLI reads each provider’s API key from a well-known environment variable — CURSOR_API_KEY, DEVIN_API_KEY, and so on (<PROVIDER>_API_KEY). Set it and go:

export CURSOR_API_KEY="YOUR_CURSOR_API_KEY"
beeps integration create --provider cursor --name "Cursor"

If your key lives under a different name, pass --api-key-env with the name of the variable. Either way the CLI reads the key from your environment at execution time, so secrets never appear on the command line or in shell history.

export SLACK_API_KEY="xoxb-..."
beeps integration create --provider devin --name "Devin"  # reads DEVIN_API_KEY

export DEVIN_API_KEY="dvn_..."
beeps integration create --provider devin --name "Devin" --api-key-env MY_DEVIN_KEY --json

Flag	Required	Description
--provider	Yes	devin, cursor, slack, or discord
--name	Yes	Display name for the integration
--api-key-env	No	Environment variable holding the API key (default: <PROVIDER>_API_KEY)

Update an integration

beeps integration update --integration-id int_abc123 --name "Slack Prod"
beeps integration update --integration-id int_abc123 --api-key-env SLACK_API_KEY

Delete an integration

beeps integration delete --integration-id int_abc123

Using integrations in relay rules

Once created, reference an integration in an agent relay rule:

beeps relay rule create --relay-id rly_abc123 \
  --name "Auto-fix with Devin" \
  --rule-type agent \
  --config '{"agentType":"devin","integrationId":"int_abc123"}'

Exit Codes

• 0 success
• 1 validation failure or API error