Help / Integrations

SendPulse (SMS)

Connect your organization's SendPulse account and 42min sends your workflow SMS through it. SendPulse bills the texts to your SendPulse balance; 42min adds no charge. You set it up on the Integrations page, under Messaging, where SendPulse is marked Recommended.

What it does

• Connect with your SendPulse API ID and API Secret (no OAuth; you paste the keys). 42min checks them with SendPulse before saving and stores them encrypted.
• Pick the sender name your texts go out under, from the senders approved in your SendPulse account.
• Send SMS steps from your workflows: SMS to invitee and SMS to host.
• Send a test SMS to check everything works.
• Track delivery: 42min checks each text's status with SendPulse, and shows it in Sent messages.

Before you start

• SMS needs a paid SendPulse plan and money on your SendPulse balance.
• You need an approved sender name. Senders are registered in SendPulse itself, per country, and SendPulse reviews each one. Approval usually takes about a week, so register one early (see SendPulse's guide to registering a sender). You can connect before it's approved; texts just can't go out until it is.

How to connect

Connecting is admin-only.

Zoom

1. In SendPulse, open your account settings, go to the API tab, and copy the API ID and API Secret.
2. In 42min, open Integrations, find SendPulse under Messaging, and click Connect.
3. Paste the API ID and API Secret and confirm. If SendPulse rejects them, check you copied both values in full.
4. Choose the Sender. Approved senders can be picked; senders still in review show as "in review" and can't be chosen yet.
5. Leave Use SendPulse to send SMS ticked (it's ticked for you when no other provider sends your SMS) and save.

Zoom

Zoom

The SendPulse tile then shows Connected, the sender, a Use to send SMS checkbox, and a link to Settings.

Settings

The SendPulse settings page has three parts:

Zoom

• Connection: who connected it, the last four characters of the API ID, the status, the last error (if any), and your live SendPulse balance. Update keys swaps in new keys (they're checked before the old ones are replaced), and Disconnect removes the connection.
• SMS sending: the Sender and Use to send SMS.
• Send a test SMS: enter a mobile number (prefilled with yours from your profile) and send. SendPulse charges it like any other SMS. You can send 5 test SMS every 10 minutes.

One provider at a time

Your organization sends all its SMS through one provider. If you also connect Twilio, ticking Use to send SMS on one tile unticks it on the other. Both connections stay saved, so you can switch back at any time.

Common pitfalls

• Texts arrive a few minutes late. SendPulse reviews every message sent through its API before delivering it, which can take up to 10 minutes. A reminder set a few minutes before the meeting can land late, so allow for that in your timing.
• No sender to choose. Your account has no approved sender yet. Register one in SendPulse, and once it's approved, choose it on the Settings page.
• Some countries fail. A sender name is approved per country. Texts to a country where your sender isn't approved are refused, and the reason shows in Sent messages.
• Connection broken. SendPulse stopped accepting the saved keys (for example, they were regenerated). Open Settings and Update keys. SMS steps are skipped until then.
• Disconnecting. 42min deletes the saved keys; nothing changes in your SendPulse account. If SendPulse was sending your SMS, workflow SMS steps are skipped until you connect a provider again.