Integration
Connect CallPage to Postpulse
When New Call fires in CallPage, your agent runs Add post in Postpulse. 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 CallPage and Postpulse 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)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 CallPage can start in Postpulse
When New Call in CallPage
then Add post in Postpulse
When New Call in CallPage
then Upload media in Postpulse
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 CallPage and Postpulse
Triggers and actions 1 trigger · 16 actions
Trigger
New CallTriggers when a new call request appears in your CallPage call history, with the visitor's phone, status and form fields.
Action
Get CallReturns one CallPage call with its status, phone, visitor details and form fields.
Action
Get ManagerReturns one manager of a CallPage widget.
Action
Get UserReturns one CallPage user, looked up by user ID or email.
Action
Get WidgetReturns one CallPage widget with its managers.
Action
List CallsReturns calls from the CallPage call history, optionally filtered by phone, widget URL or date range.
Action
List ManagersReturns the managers of a CallPage widget.
Action
List SMS MessagesReturns a CallPage widget's SMS messages.
Action
List UsersReturns the users in the CallPage account.
Action
List Voice MessagesReturns a CallPage widget's voice messages.
Action
List WidgetsReturns the account's CallPage widgets.
Action
Update Call FieldSets the value of a form field on a CallPage call.
Action
Add postSchedule a post (or save a draft) to a connected social media account via PostPulse.
Action
Get Media ImportReturns the status of a media import from a URL, with the stored file's key once it is ready.
Action
Get Uploaded Media InfoReturns the details of an uploaded media file: its name, type and size.
Action
Import media from URLImports an image or video from a public URL into PostPulse storage and waits up to 40 seconds for the import to finish, returning the storage key to attach to a post.
Action
Upload mediaUpload an image or video file to PostPulse storage in a single request and return its storage path for use as a post attachment.
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 CallPage
CallPage to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallPage to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallPage to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallPage to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallPage to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallPage to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Postpulse
HubSpot to PostpulseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PostpulseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PostpulseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PostpulseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PostpulseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PostpulseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CallPage and Postpulse, answered
What can start an automation from CallPage?
Any of CallPage's 1 trigger in the catalog, including New Call. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Postpulse when something happens in CallPage?
Any of Postpulse's 5 actions, including Upload media, Add post, Get Media Import and Get Uploaded Media Info. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Postpulse to CallPage?
Postpulse has no triggers in the catalog today, so automations start in CallPage. If you need the other direction, ask: your agent reads Postpulse's API documentation and adds it.
Do I have to build a connector for CallPage or Postpulse?
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 CallPage and Postpulse 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.