Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Marketing ]

Sendr integration for your workflows.

Connect Sendr to Collabase once and use 19 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inAn API key
CategoryMarketing
UpdatedSeptember 2026
LicenceOpen source (MIT)
Back to the directory

Sendr in Collabase

Connect Sendr to Collabase once and use 19 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Create personalized landing pages, dynamic audio, video, and manage campaigns with Sendr.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Sendr and connect your account.
  3. Add a trigger or an action to the workflow.
  • Log in to your Sendr dashboard at https://app.sendr.io.
  • Go to Settings > API Keys.
  • Click Create New Key.
  • Copy the key and paste it below.

[ Marketing ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Sendr

What can I automate with Sendr in Collabase?

Sendr brings 19 actions and 4 triggers, for example Get Account Info, List Sheets, Get Sheet, Get Sheet Columns and 15 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Sendr to Collabase?

You open the integrations in the workspace settings, choose Sendr and connect your account once, using an API key. After that all triggers and actions are available in the workflow.

Can Sendr start a workflow?

Yes. Sendr provides 4 triggers, for example New Page Render, Page Render Updated, New Contact Page Engagement and 1 more. The workflow runs as soon as the event happens.

Does the Sendr integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.