Connectors Available
Let agents hear from and act in the tools your team already uses.
A connector lets agents hear what happens in a tool your team already uses, act in it, or talk with people through it. Your own systems can send events through generic webhooks, too. The gateway checks incoming requests and keeps accepted events for the consumers that subscribe.
Event delivery works today. Actions and most channels are designed.
Provider events and generic webhook receipt are built. Telegram also works as a channel. Calling provider APIs and chatting in Slack or Discord are designed. Where it stands has the detail.
Events from your own systems
Send an order update, a completed build or an internal alert to an endpoint your project owns. Generic webhooks accept your original request body, so your system does not need a provider-specific connector.
Choose a signed request using HMAC-SHA256 with Standard Webhooks v1, or a bearer token. The gateway checks the endpoint and its credential before keeping the event. A 202 Accepted means the delivery is stored, ready for a separate consumer to process.
- Your systemSends the original body
- GatewayChecks the endpoint and credential
- Durable eventWebhookReceived stored
- Your consumerChooses and performs its action
The gateway acknowledges durable receipt. Your consumer performs the business action afterward.
Incoming request
POST /webhooks/{endpoint_id}
Content-Type: application/json
webhook-id: order-1042-created
webhook-timestamp: <current Unix seconds>
webhook-signature: v1,<computed signature>
{"event":"order.created","order_id":"order-1042"}What your consumer receives
- Event
WebhookReceived- Project
- Orders
- Endpoint
- The registered endpoint
- Delivery ID
order-1042-created- Body
- The exact original request bytes
- Auth headers
- Not forwarded to the consumer
Retries use the same delivery ID and unchanged body. The gateway authenticates each request and suppresses another stored event within the configured duplicate window. Your consumer still handles repeated processing safely and chooses the business action; receiving a webhook does not start an agent or workflow by itself.
Receiver built. Console management in preview.
The receiver supports endpoint updates, request limits and credential rotation and revocation. Endpoint setup and delivery inspection are available as a local console preview. Live console management and the first downstream business integration still need wiring.
See the authentication, delivery and setup reference.
Provider webhooks, ready for subscribers
The provider calls one URL. The gateway checks it, publishes it to a subject that names the account and the event, and keeps it in a stream so a busy or restarted agent misses nothing.
Providers call one URL
- GitHub
- Slack
- Linear
- Sentry
- Zoom
- GitLab
POST /sources/github/acme-main/webhook /sources/<source>/<integration>/webhook - VerifyThe provider's own check: a signature, a token or a signed key.
- DedupeA delivery id becomes Nats-Msg-Id, so a retry is published once.
- RoutePublished to {subject_prefix}.{event}, named for the account.
One stream per integration
- GITHUB_ACME-MAIN
github-acme-main.pull_request - GITHUB_OTHER-ORG
github-other-org.issues - ZOOM_PRIMARY
zoom-primary.meeting.ended - SLACK_WORKSPACE
slack-workspace.message
github-acme-main.>{subject_prefix}.unroutable with the reason in a header and the original body kept. Nothing dropped silently. Several accounts per provider
- route
/sources/github/acme-main/webhook- prefix
github-acme-main- stream
GITHUB_ACME-MAIN
- route
/sources/github/other-org/webhook- prefix
github-other-org- stream
GITHUB_OTHER-ORG
Google Chat events through Pub/Sub
In the preview, mention your Chat app in a space it has joined. Google Chat publishes the interaction to a Cloud Pub/Sub topic. The gateway pulls from your subscription and stores the event in JetStream for consumers.
Google Chat app → Cloud Pub/Sub → TrogonAI gateway → JetStreamFor example, with a subject prefix of google-pubsub-chat, subscribe to google-pubsub-chat.message to receive the interaction payload. The event includes the space and message that triggered it. Google Chat Events Preview
Every provider proves itself differently
Each provider signs its requests in its own way. The gateway knows each one, and a request that fails its check is refused before any agent can see it.
Each webhook carries a signed ES256 token. Every part of it has to hold up.
- Fetch the signing key by its id, then cache it
- Check the token was issued recently
- Match the body's SHA-256 to the one in the token
Datadog does not sign its webhooks, so the gateway asks for a shared token in a header instead.
- Compare the token in constant time, so timing reveals nothing
- Optionally refuse a request that is not fresh
GitHubSignature Signed with your webhook secret.
LinearSignature Signed requests, with a 60 second timestamp tolerance.
XChallenge Your consumer secret answers the CRC challenge and checks every signature.
TelegramSecret token A secret token header on every update. The gateway can register its own webhook at startup.
GitLabToken Checked against your signing token.
incident.ioSignature Checked against your signing secret.
SentrySignature Checked against your client secret.
NotionToken Checked against your verification token.
Microsoft GraphClient state The client state on each notification must match yours.
SlackSignature Signed with your signing secret. Requests older than five minutes are refused, and Slack's SSL check is answered.
ZoomSignature Signature over the timestamp and body, inside a five minute window. Zoom's URL validation is answered on the spot.
Not webhooks The gateway opens these connections itself.
DiscordBot tokenGoogle Cloud Pub/SubStreaming pull
Hear, act, talk
A connector can let agents hear what happens, act in the tool, or talk with people through it. Each card says what works today.
Events
AvailableHear what happens.
Every connector here delivers its provider's events, ready for any agent that subscribes.
linear-main.IssueActions
DesignedAct in the tool.
Agents will call provider APIs through a connection your project owns. A proxy adds the credential on the way out, so the agent never sees the key.
- Agent
- Proxy adds the credential
- Provider API
Channel
Talk with people.
Agents hold conversations inside the tool. Slack and Discord events already arrive here.
Is the deploy for the billing fix done?
It finished a few minutes ago. Every check passed.
Browse connectors
- DatadogRoute monitor alerts and events to agentsAvailable
- DiscordReact to messages and server activityAvailable
- GitHubReact to pull requests, issues and workflow runsAvailable
- GitLabReact to merge requests, issues and pipelinesAvailable
- Google ChatReceive Google Chat app interactions through Cloud Pub/SubPreview
- Google Cloud Pub/SubStream Workspace and Cloud notifications to agentsAvailable
- incident.ioBring incident updates into agent workflowsAvailable
- LinearReceive webhooks for issues, comments and moreAvailable
- Microsoft GraphReceive Teams, Outlook and calendar change notificationsAvailable
- NotionReact to page and database changesAvailable
- PlaidReact to account, transaction and item updatesAvailable
- SentryRoute errors and issue alerts to agentsAvailable
- SlackReceive messages, interactions and slash commandsAvailable
- TelegramReceive bot messages and updatesAvailable
- WhatsAppReceive messages sent to a WhatsApp Business numberPreview
- XReceive account activity from XAvailable
- ZoomReact to meetings, recordings and transcriptsAvailable
Provider connector guarantees
These guarantees describe the named provider integrations. Generic endpoints use the separate gateway webhook delivery contract.
- Proven before it is publishedEvery request passes the provider's own check, a signature, token or signed key, before any agent can see it.
- A retry arrives onceWhen the provider sends a delivery id, a redelivered webhook is recognized and published only once.
- Nothing dropped silentlyA body the gateway cannot route is published with the reason attached, so you can see it and act on it.
- Slack gets its answer in timeSlash commands and modal submissions are answered inside the three seconds Slack allows.
- Every account kept apartEach named integration has its own route, its own subjects and its own stream.
- Secrets by referenceConfiguration names an environment variable or a secret store entry. It never holds the secret itself.
- One process to runOne HTTP port for every webhook, plus the long-lived connections some providers need, with health probes.
Where it stands
- Generic webhook receiverYour own systems send authenticated HTTP events. The gateway keeps the original body in a durable delivery for your consumers.Built
- Generic webhook management in the consoleEndpoint setup and delivery inspection have a local preview. Live project-scoped management is still pending.In progress
- Webhook gateway with checks for each providerSignatures, tokens, timestamp windows and signed keys, verified before anything is published.Built
- Long-lived connectionsA Discord gateway session and Google Pub/Sub streaming pull run inside the same process.Built
- Several accounts per providerNamed integrations, each with its own route, subject prefix and JetStream stream.Built
- Interactive Slack responsesSlash commands, modal submissions and option menus answered by your responder within Slack's deadline.Built
- Telegram as a channelAgents hold conversations with people in Telegram.Built
- Credential store for provider secretsWriting, rotating, revoking and destroying secrets are recorded as events, and the running gateway refreshes from them.In progress
- Actions through project connectionsAgents call provider APIs through a proxy that holds the credential, so the agent never sees it.Designed
- Slack and Discord as channelsTheir events already arrive. Holding conversations in them is designed.Designed
Add a connector to this page
Create docs/product/connectors/<slug>.md with a connector block in its frontmatter and <ConnectorHeader /> at the top of its body. The page appears in the gallery on the next build.
---
title: GitHub
connector:
name: GitHub
summary: React to pull requests, issues and workflow runs
category: Developer tools
icon: github # a https://simpleicons.org slug; omit it and set color for a monogram tile
capabilities:
events: available # available, preview or planned
actions: planned
---The build fails on an unknown category, icon slug or capability, so a typo never ships a broken card. To build a connector rather than list one, see Add a Connector Provider.
Learn more
Understand the design
Build and operate
