Integration
Connect DoneThat and SendPulse
When New Project fires in DoneThat, your agent runs Unsubscribe User in SendPulse, or New Subscriber in SendPulse to Add Project in DoneThat. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want DoneThat and SendPulse to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What DoneThat and SendPulse can do together
From DoneThat to SendPulse
When New Project in DoneThat
then Unsubscribe User in SendPulse
When New Project in DoneThat
then Add Subscriber in SendPulse
From SendPulse to DoneThat
When New Subscriber in SendPulse
then Add Project in DoneThat
When New Subscriber in SendPulse
then Edit Project in DoneThat
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with DoneThat and SendPulse
Triggers and actions 2 triggers · 15 actions
Trigger
New ProjectTriggers when a project is created within the lookback window. Recommended Zap poll interval: 1 hour or longer.
Action
Add ProjectCreates a new DoneThat project.
Action
Archive ProjectArchives or unarchives a DoneThat project.
Action
Edit ProjectUpdates an existing DoneThat project.
Action
Find ProjectFind projects by name (optional filter).
Action
Get SummaryReturns the formatted DoneThat summary for a given date and level (day, week, month, quarter or year).
Action
SearchSearch DoneThat task and activity history.
Trigger
New SubscriberTriggers when a new subscriber is created.
Action
Add SubscriberAdds a subscriber (email address, with optional variables and tags) to a SendPulse mailing list, with single or double opt-in.
Action
Change Variable for SubscriberUpdates one or more variable values for a subscriber in a SendPulse mailing list.
Action
Create WebhookCreates an Email service webhook that sends the chosen events to a URL. SendPulse creates one webhook per event.
Action
Delete ContactRemoves a contact's email address from a SendPulse mailing list.
Action
Get SubscriberFetches one subscriber of a mailing list by email address, including their status and variables. An error occurs if the email is not in the list.
Action
List Mailing ListsReturns the mailing lists (address books) in the SendPulse account.
Action
List WebhooksReturns the Email service webhooks registered on the account, optionally only those for one event.
Action
Unsubscribe UserMarks a contact as unsubscribed in a SendPulse mailing list without deleting it.
Action
Update SubscriberUpdates the variable values (such as name, phone or city) of an existing subscriber in a SendPulse mailing list.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from DoneThat
DoneThat to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DoneThat to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DoneThat to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DoneThat to Google SheetsGoogle Sheets
DoneThat to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DoneThat to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into SendPulse
HubSpot to SendPulseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SendPulseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SendPulseGoogle Sheets
Gmail to SendPulseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SendPulseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SendPulseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
DoneThat and SendPulse, answered
What can start an automation from DoneThat?
Any of DoneThat's 1 trigger in the catalog, including New Project. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SendPulse when something happens in DoneThat?
Any of SendPulse's 9 actions, including Create Webhook, Update Subscriber, Add Subscriber and Change Variable for Subscriber. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SendPulse to DoneThat?
Yes. When something happens in SendPulse, your agent can act in DoneThat too. This page covers both directions: SendPulse's triggers and DoneThat's actions are listed here as well.
Do I have to build a connector for DoneThat or SendPulse?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.