Connections & integrations
Connect the tools your team already uses, then set up triggers that turn events in those tools into client updates automatically.
Connections are how Sennith listens to the tools your team already works in — a repository, a design file, a payment, a support ticket. Once a service is connected, you add a trigger to a project so that events there turn into updates your client sees, without you writing them by hand. This page covers the workspace Connections screen and setting up a trigger.
The Connections screen
The Connections screen shows what's available to your projects in the workspace you currently have selected. It has two sections.
Integrations
The connected services this workspace can build triggers on. Each entry shows the connected account and the service, along with who it belongs to:
- By you — a connection you added; you can remove it from the workspace.
- Shared by a member — a teammate made theirs available here.
- Company — provided by your organization for everyone.
Click Add to make one of your own connected accounts available in this workspace. If you have none yet, connect an account first in your profile — the screen links you there.
Adding a connection to a workspace makes it usable there; it doesn't change who owns it. Your login details for the service always stay with you.
SMTP
The sending profiles available for this workspace's client mail. Each shows its sender address and owner, mirroring the same "By you / shared / Company" ownership. You can also star one as this workspace's default sender (unless your organization has locked a default in place).
Setting up a trigger
Triggers live on a project. Open a project, find the Integrations section, and add one. Sennith walks you through it in three steps.
Source & data. Choose the service (search or pick from the grid), name the trigger, then choose the account and the specific thing to watch — a repository and branch, a board, a design file, a form, and so on. You also pick which events should fire the trigger (for example, a deployment succeeding, an invoice being paid, or a task marked done).
Delivery. Decide whether the resulting update is marked important, and how the client is emailed — no email, queued to the outbox for your approval, or sent directly. You can also pick an email template. Finally, set the update's visibility: public, internal (team only), or automatic.
Text & display. Choose how each update reads — auto-generated, one of your update templates, or a custom template you write with placeholders that get filled in from the event.
Save, and the trigger appears in the project's Integrations list. From there you can switch it between Active and Paused, edit it, copy its token, or delete it.
Some visibility and delivery options are part of Sennith Pro. On a free plan, updates are public and the Pro-only choices show an upgrade prompt.
Reconnecting an orphaned trigger
If the connection behind a trigger is removed, the trigger shows an Orphaned badge and stops firing. Open it and choose one of your own connections for that same service to reconnect it — no need to rebuild the trigger.
What you can connect
Sennith supports a wide range of services, including code and deployment tools (GitHub, GitLab, Vercel), project and task tools (Jira, Linear, Asana, Trello, ClickUp, Notion), design (Figma), payments and finance (Stripe, QuickBooks, Xero, Pipedrive, Lexoffice, sevdesk), commerce (Shopify), support and CRM (Zendesk, Intercom, HubSpot), scheduling and forms (Calendly, Typeform), files (Google Drive, Dropbox), messaging (Slack, Microsoft Teams), HR (Personio), monitoring (Sentry), and generic automation via Zapier or a custom webhook.
The exact list keeps growing. If a service isn't there yet, a custom webhook or a Zapier connection can usually bridge the gap.
Self-hosted instances
Some providers (for example GitHub, GitLab, Jira, Sentry) also run on your own servers. For those, Sennith can connect to a self-hosted instance instead of the vendor's cloud. You provide the instance's base URL (must be https://) and one authentication method the provider supports — OAuth (client ID + client secret), a Personal Access Token, or basic auth (username + token). Self-hosted connections are part of Enterprise; on other plans the option shows an upgrade prompt.