SendPulse
Email MarketingManage SendPulse address books and their contacts, send transactional email through the SMTP service, and report on campaign statistics. Agents sync leads into mailing lists with merge-field variables and look up a contact's subscription state by email.
What This Integration Enables
SendPulse puts mailing lists and transactional SMTP under one roof, which matters more than it sounds: the systems that know your customers, the store, the form tool, the billing platform, can feed both the marketing audience and the one-off sends through a single connector. FlowRunner agents use that shape. They enroll contacts with merge-field variables at the moment of the triggering event, fire receipts and confirmations from verified senders, and keep list membership honest with reviewed hygiene sweeps. - Sync customers, leads, and form respondents into address books with merge-field variables attached - Send order confirmations, receipts, and other transactional email from automated workflows - Maintain list membership as records change in other systems, with [human-in-the-loop](/concepts/human-in-the-loop) review on removals - Look up any contact's global subscription state by email before acting on them - Report campaign performance, sent, opened, clicked, into spreadsheets and chat
Without FlowRunner
With FlowRunner
Use Case Scenarios
The welcome that arrives with the receipt
A new customer fires from [Shopify](/integrations/shopify). The agent calls Add Emails to Address Book to enroll them in the newsletter list with their name and first-order details as variables, then Send Transactional Email to deliver the order confirmation immediately. The double opt-in confirmation SendPulse sends for the list runs its course independently, so the receipt never waits on the subscription. Two different kinds of email, one event, correctly sequenced.
Form answers become personalization fuel
Signups collect in [Typeform](/integrations/typeform), including a question about what the respondent wants to hear about. The agent adds each respondent to the matching address book with their answers written as merge-field variables. The next campaign's template references those variables, so the first email a subscriber receives quotes their own words back to them, and nobody edited a spreadsheet to make that happen.
The campaign report that posts itself
Every Monday, the agent runs List Campaigns and writes each campaign's sent, opened, and clicked counts to [Google Sheets](/integrations/google-sheets), then posts the latest send's numbers to [Slack](/integrations/slack). When a campaign's open rate falls outside the usual range, the message flags it. The team discusses performance with the numbers already on the table instead of spending the meeting fetching them.
Human-in-Loop Highlight
Remove Emails from Address Book looks reversible and is not. Removing an address unsubscribes it from that list, and the way back runs through SendPulse's double opt-in: re-adding the contact triggers a confirmation email, and a real fraction of any audience never clicks confirmation emails. A hygiene sweep with a mis-keyed filter does not make a mistake you can undo; it permanently sheds subscribers you paid to acquire. So FlowRunner stages every removal batch for review: the agent shows the marketer which addresses it wants to drop, why, and from which list. The sweep runs monthly at machine speed. The shrink button waits for a person.
Agent Capabilities
9 actionsAddress Books
3- Create Address Book Creates a new mailing list with the given name and returns its ID, ready for contact operations.
- Get Address Book Retrieves a single address book by ID, including name and subscriber counts: all, active, unsubscribed.
- List Address Books Retrieves the account's mailing lists with each book's ID, name, and subscriber counts, paginated via limit and offset.
Contacts
4- Add Emails to Address Book Adds one or more email contacts to an address book, each with optional merge-field variables. By default SendPulse sends a double opt-in confirmation unless the book is configured for single opt-in. The enrollment write behind every sync.
- Get Contact Retrieves a contact's global state across all address books: status, rating, source, and date added. The lookup that answers whether this person can be emailed at all.
- List Emails in Address Book Retrieves the contacts stored in an address book with each contact's status and variables, paginated via limit and offset. The read behind exports, audits, and hygiene sweeps.
- Remove Emails from Address Book Removes one or more email contacts from an address book by exact address, unsubscribing them from that list only. The operation this page's human gate exists for.
Campaigns
1- List Campaigns Retrieves the account's email campaigns with ID, name, subject, send date, status, and aggregate statistics: sent, opened, clicked. The feed behind performance reporting.
Transactional
1- Send Transactional Email Sends a single transactional email through the SendPulse SMTP service, with subject, verified sender, one or more recipients, and HTML or plain-text bodies. The HTML body is Base64-encoded automatically. Returns a result flag and message ID.
Frequently Asked Questions
What can FlowRunner do with SendPulse?
FlowRunner agents can run List Address Books, Create Address Book, and Get Address Book in SendPulse, plus 6 more actions.
Does connecting SendPulse to FlowRunner require OAuth?
Yes. SendPulse connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can SendPulse trigger a FlowRunner workflow automatically?
SendPulse doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SendPulse
$100 in credits. No card required. Connect in minutes.