Integrations

Works with events from anywhere.

Any event from the outside world can start a run. Agents act back through the same checked gateway.

Request access
Built-in connectors

Slack, GitHub, Jira and Zendesk, ready to use.

Events come in and actions go out, with replies in the same thread.

Slack

Socket Mode

Events in

  • app_mention
  • message
  • reaction_added
  • stop_agent

Actions out

  • post
  • react
  • upload
  • read_thread
  • lookup_user

Thread replies, with 👀 while it works.

GitHub

GitHub App webhook · HMAC

Events in

  • issues
  • issue_comment
  • pull_request
  • pull_request_review
  • pull_request_review_comment
  • check_suite
  • workflow_run

Actions out

  • get_issue
  • comment
  • create_issue
  • label
  • open_pr
  • request_review
  • merge_pr

Issue and pull request comments, with a 👀 reaction.

Jira

Site webhook with a secret

Events in

  • issue_created
  • issue_updated
  • comment_created

Actions out

  • search
  • get_issue
  • comment
  • transition
  • create_issue
  • assign
  • attach

Issue comments.

Zendesk

Polls every 60 s

Events in

  • new tickets
  • new comments

Actions out

  • get_ticket
  • comment
  • update_ticket

Ticket comments.

Anything else

Connect the rest without writing a connector.

Add any MCP server, send events in with a webhook, or start runs on a schedule.

Any MCP server

Add its URL, with no auth, a bearer token or OAuth. Its tools pass the same checks as every other call.

pagerduty.list_incidents
linear.create_issue ✓

Inbound webhooks

A signed webhook starts a run. Each hook has its own HMAC or bearer secret.

POST /hooks/support/new-lead
● run started

Outbound run webhooks

Outbound webhooks report the result.

run.completed → your URL

Schedules

Cron starts, after waits, and watches like "ping me when this PR merges".

start: cron "0 9 * * MON-FRI"
after: 2h

Web chat

Talk to a project's agents in the console chat page.

Priya: summarise SUP-41

Platform events

Run lifecycle, record changes, artifact publishes, approval decisions and custom emit events can start more work.

on: run.completed
on: emit ●
How connections work

As Hinzel, or as the person who asked.

Each connection is an encrypted credential for one outside account. The gateway adds it to each call, so agents never hold your keys.

agent no credential gateway credentials encrypted · KMS credential added Jira as Hinzel as Priya jira.comment jira.comment agent no credential gateway credentials KMS credential added Jira as Hinzel as Priya
  • Encrypted at rest. Connection secrets are encrypted with KMS-managed keys.
  • Agents never hold keys. The gateway adds the credential to each call. The agent never sees it.
  • Write-only secrets. Only org admins add shared credentials. Secrets are write-only.
app_install

As Hinzel

An org admin installs the Slack app or the GitHub App. Replies and actions come from the bot, @hinzel.

org

As a shared account

An org admin adds an API token, a service account or an MCP server URL. Used for Jira, Zendesk, PagerDuty and MCP servers.

user

As the person who asked

Each person connects their own account. They see every action taken with it, and can revoke it.

One set of rules

Every action goes through the same rules.

Built-in actions and MCP tools pass the same gateway. Each project's rules decide which actions run, which need a person and which never run.

How the gateway works

Put a fleet to work this week.

Hinzel is in early access. Tell us about your team and we will set up your first project with you.