Integrations overview

An integration connects an external business tool to your pipelines: to read data (revenue, team activity, calendar) or to act (publish a campaign, create an event, fetch a call recording).

Unlike a channel, which triggers a pipeline, an integration is consumed inside a pipeline — by a dedicated node or by a tool made available to an agent.

The "BYO" (Bring Your Own) model

All integrations are BYO: you provide your own credentials (API key, token, OAuth account) in the admin panel. betool never inserts itself between you and the provider, never stores any secret in clear text on the client side, and charges no margin on these calls — you pay the provider directly.

Some managed integrations (LinkedIn, Google) additionally offer a shared vendor fallback: if your organization has not configured its own account, betool can route the call through a pooled account (resolution your account > shared account). See each integration's page.

Catalogue

Finance & payment

• Stripe — read your revenue, MRR and subscriptions; generate payment links.
• Enable Banking — open banking (PSD2/AIS): read accounts and transactions, treasury snapshot per currency.

Development & production

• GitHub — team productivity report per developer, CI status.
• Jira — read and write tickets (Cloud or Server/Data Center).

Communication & messaging

• Slack — receive and send messages (Events API + chat.postMessage).
• SMS — send and receive SMS via AllMySMS (replies and delivery receipts).

CRM, marketing & productivity

• GTM suite — HubSpot, Notion, Airtable, Brevo, Mailchimp, Calendly, Typeform, Shopify, Microsoft 365 and Monday.com.

Productivity & advertising

• Google — Calendar, Sheets, Drive, Google Ads (reports, conversion uploads), postal address validation.
• LinkedIn Ads — end-to-end advertising campaign publishing.

Telephony

• Kavkom — fetch call recordings from a cloud PBX.

How it is consumed in a pipeline

Two forms, depending on the integration:

1. A dedicated node — placed in the pipeline, it calls the provider and publishes the result into the context (e.g. stripe_report, github_report, jira_report, enablebanking_report, slack_outbound, linkedin_ads_publish). Downstream nodes consume the output like any other piece of data. Nodes that act outward (send, create, publish) are exactly-once: no duplicate on retry.
2. An agent tool — made available to an agent node, which decides when to call it (e.g. google.calendar_list_events, jira.create_issue, slack.post_message, stripe.create_payment_link). See No-code actions.

Security

• Secrets are encrypted at rest and are never exposed in a GET response (the front end only sees a boolean key configured: yes/no).
• Every call is scoped to your organization: one org's integration is never visible to or usable by another.
• Outbound calls are protected against SSRF and logged.

See Security → Principles.