Callback24 for AI agents

Agents read Callback24 at once. Changes and sends are held for a person's approval by default.

About Callback24

Callback24 provides account APIs for managing phone calls, users, services, and routing groups.

What an agent can do in Callback24

Every Callback24 action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Callback24 without asking first. 10 actions.

  • Get Current UserReturn the Callback24 user identity associated with the connected API token.
  • Get GroupReturn one Callback24 routing group by ID with its service ID and localized names.
  • Get Phone CallReturn detailed metadata, tags, and assigned-user information for one Callback24 phone call.
  • Get Phone Call RecordingReturn the recording URL for one recorded phone call.
  • Get ServiceReturn one Callback24 service with opening hours, routing groups, and assigned users.
  • Get UserReturn one company user by Callback24 user ID.
  • List GroupsReturn all Callback24 routing groups with their service IDs and localized names.
  • List Phone CallsReturn one page of phone-call history, optionally filtered by type, date range, phone number, users, or services. Use limit with either page or offset to paginate; Callback24 does not document precede
  • List ServicesReturn all Callback24 services with their nested groups, assigned users, and opening hours.
  • List UsersReturn all company users visible to the connected Callback24 account.

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 17 actions.

  • Assign User to ServiceAssign a Callback24 user to a service, optionally within a routing group.
  • Batch Assign Users to ServiceSequentially assign 1-25 Callback24 users to one service. This operation is non-atomic and has no rollback: processing stops after the first provider failure, malformed success response, or transport
  • Batch Remove Users from ServiceSequentially remove 1-25 users from a Callback24 service. This operation is non-atomic and provides no rollback: processing stops after the first provider failure, malformed success response, or trans
  • Cancel Upcoming Phone CallsIrreversibly bulk-cancel every upcoming phone call matching a phone number or lead reference. Optionally narrow the destructive operation by earliest scheduled time and service. The reason is permanen
  • Create GroupCreate a routing group within a Callback24 service, with optional localized names.
  • Create Phone CallCreate or schedule a real phone call in Callback24. This action can trigger customer-visible telephony to the supplied recipient phone number.
  • Create ServiceCreate a Callback24 service for a website. This can create customer-visible widget or routing configuration.
  • Create UserCreate a company user in Callback24. This may send an invitation and may consume an account seat.
  • Delete GroupPermanently and irreversibly delete one Callback24 routing group by group ID. This deletion cannot be undone.
  • Delete ServicePermanently and irreversibly delete one Callback24 service and its associated routing and customer-facing widget configuration. This operation cannot be undone.
  • Delete UserPermanently and irreversibly delete one company user by Callback24 user ID. This operation cannot be undone.
  • Remove User from ServiceRemove a Callback24 user's assignment from a service, optionally within a routing group.
Show all 17
  • Update GroupUpdate one or more localized names for a Callback24 routing group.
  • Update Phone CallUpdate editable metadata for an existing phone call without changing its explicit cancellation or start/end status fields. Provide at least one editable field in addition to call_id.
  • Update Phone Call StatusSet a phone call's cancelled flag and/or recorded start and end times; this changes operational call state. Provide at least one of cancelled, call_start_time, or call_end_time.
  • Update ServiceChange the website configured for an existing Callback24 service.
  • Update UserUpdate one or more profile or role fields for an existing Callback24 company user. Provide at least one of first_name, last_name, email, phone_number, or role.

Changes wait in Needs you

Changes and sends in Callback24 are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Callback24 questions

Can an agent change data in Callback24 on its own?

Not by default. Changes and sends in Callback24 are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Callback24?

This connector lists 10 read actions. Reads run at once, without waiting for approval.

How does Callback24 connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Callback24 to your agents.