Integration
Connect Halo Service Solutions to Teambook
When New Ticket fires in Halo Service Solutions, your agent runs Add Task in Teambook. 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 Halo Service Solutions and Teambook 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 Halo Service Solutions can start in Teambook
When New Ticket in Halo Service Solutions
then Add Task in Teambook
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 Halo Service Solutions and Teambook
Triggers and actions 2 triggers · 48 actions
- New Ticket
Triggers when a new ticket is logged in Halo.
- Ticket Updated
Triggers when a ticket is created or updated in Halo.
- Add action to ticket
Adds a new action (note, update or outcome) to an existing Halo ticket.
- Add project
Creates a new project in Halo and returns the created project record.
- Create Site
Creates a new site for a customer in Halo.
- Create Ticket
Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.
- Create User
Creates a new end user in Halo under the chosen site.
- Get customer
Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.
- Get project
Returns a single Halo project by its ID, including its details and custom fields.
- Get ticket
Returns a single Halo ticket by its ID, optionally with extra details and its last action.
- Get user
Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.
- List customers
Returns a list of customers (clients) in Halo, optionally filtered by search text or top level.
- List tickets
Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.
- List users
Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.
- Update ticket
Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.
- Update user
Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.
- Add Actual log
Creates one or more time-tracking actual logs in a batch.
- Add Booking
Creates one or more bookings in a batch.
- Add Client
Creates a client record.
- Add Task
Creates a task, optionally scoped to a project (omit project_id for account-wide task).
- Create Project
Create a Project inside Teambook
- Create User
Creates a teambook User
- Deactivate User
Deactivates a Teambook user so they can no longer be booked or sign in, without deleting their history.
- Delete Actual log
Deletes an actual log by id.
- Delete Booking
Removes a single booking from Teambook.
- Delete Project
Deletes a project by id.
- Delete Task
Deletes a task from the Teambook account.
- Delete User
Deletes a user from the Teambook account.
- Get Actual log
Retrieve a single Teambook actual log (time entry) by its id.
- Get Booking
Retrieve a single Teambook booking (a user's assignment to a project on a date for a duration) by its id.
- Get Client
Retrieves a single client by id.
- Get Project
Retrieves a single project by id.
- Get Task
Retrieves a single task by id.
- Get Team
Retrieve a single Teambook team by its id.
- Get User
Retrieve a single Teambook user by id.
- List Actual logs
Lists actual logs (timesheet entries), filterable by user_id, project_id, since, range.
- List Bookings
Lists bookings, optionally filtered by team, user, project and date window. Returns the first page of up to 100 bookings.
- List Clients
Returns every client in the Teambook account.
- List Project capacities
Lists project capacity entries (days reserved per project per month) entered on the Capacity by Project page.
- List Projects
Lists all projects in the Teambook account.
- List Tasks
Lists all tasks.
- List Teams
Lists all teams in the Teambook account.
- List User capacities
Lists monthly capacity-reservation rows per user, filterable by user_id and since (first day of month).
- List Users
Lists all users in the Teambook account.
- Update Actual log
Edits an actual log's project, user, date, duration, task, payroll_item, approved, or comment.
- Update Booking
Updates an existing Teambook booking; only the fields you fill in are changed.
- Update Client
Edits a client's name, phone_number, or email.
- Update Project
Edits a project's fields (name, code, active, color, kind, estimated, notes, client_id, manager_id, dates, custom_fields).
- Update Task
Edits a task's name or project_id.
- Update User
Edits a user's first_name, last_name, email, role, billable, time_zone, phone_number, language, or schedule.
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 Halo Service Solutions
Halo Service Solutions to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Halo Service Solutions to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Halo Service Solutions to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Halo Service Solutions to MailchimpMailchimp marketing automation and email platform.
Halo Service Solutions to StripeStripe is a payment processing platform for online businesses.
Halo Service Solutions to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Teambook
Google Sheets to TeambookGoogle Sheets
Gmail to TeambookGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TeambookGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Halo Service Solutions and Teambook, answered
What can start an automation from Halo Service Solutions?
Any of Halo Service Solutions's 2 triggers in the catalog, including New Ticket and Ticket Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Teambook when something happens in Halo Service Solutions?
Any of Teambook's 34 actions, including Create Project, Create User, Update Actual log and Update Booking. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Teambook to Halo Service Solutions?
Teambook has no triggers in the catalog today, so automations start in Halo Service Solutions. If you need the other direction, ask: your agent reads Teambook's API documentation and adds it.
Do I have to build a connector for Halo Service Solutions or Teambook?
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 Halo Service Solutions and Teambook 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.