Integrations

Last updated on September 29, 2026

TofuPilot integrates with the tools your team already uses through Workflows. A workflow ties a trigger, such as a run landing, a unit being created, or a schedule firing, to one or more actions on a connected provider.

How integrations fit together

Every workflow you build has three parts that compose into a single pipeline:

  1. Trigger: a TofuPilot event such as a run landing, a unit being created, or a schedule firing.
  2. Control flow (optional): a filter, if/else, or switch that shapes the path downstream nodes take.
  3. Actions: calls to integration providers that do the actual work.

Each action exposes its result as a variable, and downstream actions can read from it. For example, you can listen on a run_created trigger, filter to failing runs, open a Linear issue, and then post a Slack message that links to the new ticket.

IntegrationDirectionAuth
EmailOutboundTofuPilot-managed
SlackOutboundIncoming webhook URL
DiscordOutboundWebhook URL
HTTPOutboundConfigurable per request
OdooOutboundOAuth or API key
InvenTreeOutboundAPI token
LinearOutbound + inboundOAuth app

Permissions

Connecting a provider and rotating its credentials requires the Admin or Owner role. Developers create, edit and delete workflows on top of the existing connections. Viewers can read workflows and connections, and Operators see neither. See access roles for the full table.

How is this guide?

On this page