[ Marketing ]
Maileroo integration for your workflows.
Connect Maileroo to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
Maileroo in Collabase
Connect Maileroo to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Email Delivery Service with Real-Time Analytics and Reporting
How to connect it
- Open the integrations in the workspace settings.
- Choose Maileroo and connect your account.
- Add a trigger or an action to the workflow.
- Navigate to Domains.
- Click on the domain you want to use.
- Click on the Create sending key under the API section.
- Click New Sending Key.
- Copy the key under the Sending Key column.
- Navigate to Verification API.
Maileroo triggers
Maileroo does not start a workflow on its own. You use its actions after any other trigger.
Maileroo actions
| Name | Description | Fields |
|---|---|---|
| Send Email | Sends an email using the Maileroo API. |
+ 5
|
| Send Email using Template | Sends an email from an existing template. |
+ 5
|
| Verify Email | Verifies an email address. | |
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Marketing ]
Related integrations
Tools that often share a workflow.
Questions about Maileroo
What can I automate with Maileroo in Collabase?
Maileroo brings 4 actions and 0 triggers, for example Send Email, Send Email using Template, Verify Email and Custom API Call. You combine them in a workflow without code and mix them with every other integration.
How do I connect Maileroo to Collabase?
You open the integrations in the workspace settings, choose Maileroo and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Does the Maileroo 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.