Skip to main content
Connections expose external systems and capabilities to your Thygon workflows and agents. By configuring connections, you grant Thygon the credentials and authorization necessary to interact with your existing software stack—such as posting messages, creating issues, or fetching data.

​
How connections work

Connections bridge the gap between Thygon’s ledger and external SaaS tools. The model consists of two key components:
  1. Connection Providers: The templates that define the authentication mechanisms (e.g., OAuth2, API Keys), configuration requirements, and API capabilities of a specific external service.
  2. Connections: Your configured instances of a provider, containing the specific credentials and settings for your organization.
┌──────────────────────────┐     credentials & config     ┌─────────────┐
│   Connection Provider    │ ───────────────────────────▶ │ Connection  │
│ (e.g., Slack, GitHub)    │                              │  (Active)   │
└──────────────────────────┘                              └─────────────┘

​
Credential security

Thygon manages credentials securely within the Connection Service. Credentials are encrypted at rest and never exposed to the public API or workflow scripts. Workflows refer to connections by their configured ID or handle, and the runtime service handles token injection and signature generation behind the scenes.

​
Status of external integrations

The following table lists the supported connection providers and their current availability:
ProviderTypeStatusCapabilities
SlackCollaborationAvailablePost messages, create channels, handle interactive button clicks.
GitHubCode HostingAvailableListen to pull request events, query repositories, manage issues.
LinearProject ManagementAvailableQuery issues, update ticket statuses, track project milestones.
JiraProject ManagementBetaSync tasks, track epics, receive webhook updates.
ZendeskCustomer SupportBetaReceive new support ticket events, retrieve ticket details.
ClickUpProject ManagementPlannedSync workspace tasks and lists.
StripePayment & BillingPlannedMonitor invoice events and update billing entities.

​
Utilizing connections in workflows

Once configured, you can reference a connection in your workflow steps or assign it to an agent to grant tool-use capabilities. 
steps:
  - name: send_slack_notification
    type: action
    connection: slack
    action: post_message
    args:
      channel: "#ops-alerts"
      text: "Workflow run completed successfully."