[ Marketing ]
SendFox integration for your workflows.
Connect SendFox to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
SendFox in Collabase
Connect SendFox to Collabase once and use 4 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Email marketing made simple
How to connect it
- Open the integrations in the workspace settings.
- Choose SendFox and connect your account.
- Add a trigger or an action to the workflow.
- In SendFox, open Settings → Connections → API tokens, or go to sendfox.com/account/oauth.
- Under Personal Access Tokens, click Create New Token.
- Enter a name for the token and click Create.
- Copy the token right away (SendFox shows it only once) and paste it here.
SendFox triggers
SendFox does not start a workflow on its own. You use its actions after any other trigger.
SendFox actions
| Name | Description | Fields |
|---|---|---|
| Create List | Create a contact list in SendFox |
|
| Unsubscribe Contact | Stop all SendFox emails to a contact |
|
| Create Contact | Add a contact to SendFox, optionally to one of your lists |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Marketing ]
Related integrations
Tools that often share a workflow.
Questions about SendFox
What can I automate with SendFox in Collabase?
SendFox brings 4 actions and 0 triggers, for example Create List, Unsubscribe Contact, Create Contact and Custom API Call. You combine them in a workflow without code and mix them with every other integration.
How do I connect SendFox to Collabase?
You open the integrations in the workspace settings, choose SendFox and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Does the SendFox 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.