Integration
Connect Callback24 and Pipefy
When New Call Request fires in Callback24, your agent runs Create Record in Pipefy, or Moved Card in Pipefy to Add User to Service in Callback24. 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 Callback24 and Pipefy 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 Callback24 and Pipefy can do together
From Callback24 to Pipefy
When New Call Request in Callback24
then Create Record in Pipefy
When Call Event in Callback24
then Update Database Record in Pipefy
From Pipefy to Callback24
When Moved Card in Pipefy
then Add User to Service in Callback24
When New Card in Pipefy
then Create User in Callback24
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 Callback24 and Pipefy
Triggers and actions 8 triggers · 35 actions
Trigger
Call EventTriggers when a Callback24 call is logged or its end time is recorded (the call ends).
Trigger
New Call RequestTriggers when a new phone call request appears in Callback24 call history.
Action
Add User to ServiceAssigns a Callback24 user to a service, optionally within a routing group.
Action
Cancel Upcoming Phone CallsCancels all upcoming Callback24 calls for a phone number or lead reference.
Action
Create a Phone CallCreates or schedules a phone call in Callback24, which places a real call to the number.
Action
Create GroupAdds a routing group to a Callback24 service.
Action
Create ServiceAdds a Callback24 service for a website.
Action
Create UserAdds a user to the Callback24 company.
Action
Delete GroupDeletes a Callback24 routing group.
Action
Delete ServiceDeletes a Callback24 service.
Action
Delete UserDeletes a Callback24 user.
Action
Get Call RecordingReturns the recording link of a Callback24 phone call.
Action
Get GroupReturns one Callback24 routing group by ID.
Action
Get Phone CallReturns one Callback24 phone call by ID, with its schedule, times, contact and tags.
Action
Get ServiceReturns one Callback24 service by ID, with opening hours and routing groups.
Action
Get UserReturns one Callback24 user by ID: name, email, phone number and role.
Action
List GroupsReturns every Callback24 routing group.
Action
List Phone Call HistoryReturns Callback24 phone call history, filtered by type, date range or phone number.
Action
List ServicesReturns every Callback24 service (website) with its routing groups and users.
Action
List UsersReturns every user in the Callback24 company.
Action
Remove User from ServiceRemoves a Callback24 user from a service.
Action
Update GroupRenames a Callback24 routing group.
Action
Update Phone CallUpdates a Callback24 phone call's details such as schedule, assignee, contact and comments.
Action
Update Phone Call StatusCancels a Callback24 phone call or sets its start and end times.
Action
Update ServiceUpdates a Callback24 service's website.
Action
Update UserUpdates a Callback24 user's name, email, phone number or role.
Trigger
Done CardTriggers when a card is done.
Trigger
Moved CardTriggers when a card is moved.
Trigger
New CardTriggers when a new card is created.
Trigger
New Database RecordTriggers when a new record is created.
Trigger
Updated Card FieldTriggers when a card field is updated.
Trigger
Updated Record FieldTriggers when a record field is updated.
Action
Create CardCreates a card in a Pipefy pipe, filling in its start form fields.
Action
Create RecordCreates a new table record.
Action
Delete CardPermanently deletes a card from its pipe.
Action
Delete Database RecordDelete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
Action
Find CardReturns the cards in a pipe whose chosen field matches the specified value.
Action
Find Database RecordsFind a database records by title.
Action
Get CardRetrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
Action
Get Database RecordFetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
Action
Move CardMoves a Pipefy card to another phase of its pipe.
Action
Update Card FieldSets a new value on one field of an existing Pipefy card.
Action
Update Database RecordUpdate a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
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 Callback24
Callback24 to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Callback24 to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Callback24 to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Callback24 to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Callback24 to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Callback24 to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pipefy
GrowSurf to PipefyGrowSurf is referral software for B2C and B2B tech companies.
HubSpot to PipefyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PipefyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PipefyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PipefyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Callback24 and Pipefy, answered
What can start an automation from Callback24?
Any of Callback24's 2 triggers in the catalog, including New Call Request and Call Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefy when something happens in Callback24?
Any of Pipefy's 11 actions, including Create Card, Create Record, Update Card Field and Update Database Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefy to Callback24?
Yes. When something happens in Pipefy, your agent can act in Callback24 too. This page covers both directions: Pipefy's triggers and Callback24's actions are listed here as well.
Do I have to build a connector for Callback24 or Pipefy?
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 Callback24 and Pipefy 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.