Integration
Connect Pyrus and Sailthru
When New Form Task fires in Pyrus, your agent runs Create / Update User Profile in Sailthru, or Lists in Sailthru to Add Task Comment in Pyrus. 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 Pyrus and Sailthru to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Pyrus and Sailthru can do together
From Pyrus to Sailthru
When New Form Task in Pyrus
then Create / Update User Profile in Sailthru
When New Form Task in Pyrus
then Send a Custom Event in Sailthru
From Sailthru to Pyrus
When Lists in Sailthru
then Add Task Comment in Pyrus
When Lists in Sailthru
then Find Form Tasks in Pyrus
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 Pyrus and Sailthru
Triggers and actions 2 triggers · 14 actions
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
Trigger
ListsTriggers when a new list is created in Sailthru.
Action
Create / Update User ProfileCreates a Sailthru user profile, or updates the existing one, including its keys, custom fields, list memberships and opt-out status.
Action
Get User ProfileReturns a Sailthru user profile — its keys, custom fields, list memberships, engagement and opt-out status — by email or another profile key.
Action
Send a Custom EventSends a custom event for a Sailthru user, which can start a Lifecycle Optimizer flow or trigger.
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 Pyrus
Pyrus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pyrus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pyrus to StripeStripe is a payment processing platform for online businesses.
Pyrus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pyrus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pyrus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Sailthru
HubSpot to SailthruHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SailthruGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SailthruGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SailthruGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SailthruGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to SailthruMailchimp marketing automation and email platform.
Questions
Pyrus and Sailthru, answered
What can start an automation from Pyrus?
Any of Pyrus's 1 trigger in the catalog, including New Form Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sailthru when something happens in Pyrus?
Any of Sailthru's 3 actions, including Create / Update User Profile, Send a Custom Event and Get User Profile. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Sailthru to Pyrus?
Yes. When something happens in Sailthru, your agent can act in Pyrus too. This page covers both directions: Sailthru's triggers and Pyrus's actions are listed here as well.
Do I have to build a connector for Pyrus or Sailthru?
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.
Can my AI client use Pyrus and Sailthru without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.