Integration
Connect Callback24 and Pipefile
When New Call Request fires in Callback24, your agent runs Send Request in Pipefile, or File Request Created in Pipefile 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 Pipefile 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 Pipefile can do together
From Callback24 to Pipefile
When New Call Request in Callback24
then Send Request in Pipefile
When Call Event in Callback24
then Create Contact in Pipefile
From Pipefile to Callback24
When File Request Created in Pipefile
then Add User to Service in Callback24
When File Request Created in Pipefile
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 Pipefile
Triggers and actions 3 triggers · 34 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
File Request CreatedTriggers when a file request is created.
Action
Add File Request From TemplateCreate a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
Action
Create ContactAdd to contacts
Action
Delete ContactDelete a contact by id. Returns 204 No Content on success.
Action
Get ContactRetrieve one contact by id.
Action
Get File RequestRetrieve detailed information about one file request by id, including contents, items, files, and tracking events.
Action
List ContactsRetrieve a paginated list of contacts, filterable by name/email/phone partial match.
Action
List File Request TemplatesRetrieve the list of file request templates available for creating new file requests, with optional name search.
Action
Search File RequestsFinds all file requests matching this search query (contact name, email, tags, etc).
Action
Send RequestCreate and send a new request
Action
Update ContactUpdate name/email/phone of an existing contact by id.
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 Pipefile
HubSpot to PipefileHubSpot is your all-in-one stop for all of your marketing software needs.
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
CM.com to PipefileCM.com — create excellent conversational customer experiences and turn any conversation into a conversion.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Google Sheets to PipefileGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PipefileGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Callback24 and Pipefile, 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 Pipefile when something happens in Callback24?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to Callback24?
Yes. When something happens in Pipefile, your agent can act in Callback24 too. This page covers both directions: Pipefile's triggers and Callback24's actions are listed here as well.
Do I have to build a connector for Callback24 or Pipefile?
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 Pipefile 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.