Tembo Connections

Tembo connections let Firetiger launch coding-agent runs on Tembo when issues are created or updated. Each connection runs in one of two modes:

Task mode — Firetiger POSTs to /task/create with the prompt + GitHub repo for an ad-hoc agent run.
Automation mode — Firetiger POSTs to /automation/{key}/trigger with issue context as the event payload, letting you pre-configure agent, skill, and model selection inside Tembo.

Tembo sits alongside Firetiger’s other coding-agent integrations (Cursor). Pick the one that matches the workflow you want.

Recommended: Create and manage connections via the web UI at https://ui.cloud.firetiger.com/settings/connections

Setup

Sign in to app.tembo.io
Navigate to Settings → API Keys and copy your bearer token
(Automation mode only) Create the automation in Tembo first and copy its key or UUID

Connection Parameters

Required Parameters

Parameter	Type	Description
`api_key`	string	Bearer token for `api.tembo.io`

Mode (exactly one)

Task Mode

"task": {
  "default_agent": "claudeCode:claude-sonnet-4-6"
}

Field	Description	Default
`default_agent`	Tembo agent identifier passed as the `agent` field on `/task/create`	Tembo’s org-level default

Automation Mode

"automation": {
  "automation_key": "<automation-key-or-uuid>"
}

Field	Description
`automation_key`	Tembo automation key or UUID — required

Example Connections

Task mode:

{
  "display_name": "Tembo Ad-Hoc",
  "description": "Tembo task launcher for one-off coding-agent runs from Firetiger issues",
  "connection_details": {
    "tembo": {
      "api_key": "<token>",
      "task": { "default_agent": "claudeCode:claude-sonnet-4-6" }
    }
  }
}

Automation mode:

{
  "display_name": "Tembo Triage Automation",
  "description": "Triggers the 'incident-triage' Tembo automation with issue context",
  "connection_details": {
    "tembo": {
      "api_key": "<token>",
      "automation": { "automation_key": "incident-triage" }
    }
  }
}

Best Practices

Use automation mode when agent/skill/model selection is stable — it keeps that configuration in Tembo where the rest of your team can edit it
Use task mode for experimental workflows — easier to iterate on the prompt from Firetiger without redeploying a Tembo automation
One connection per automation — connections are 1:1 with a launch target, so a separate connection per workflow is the cleanest mapping