Integration
Connect BotStar to Clockodo
When New CMS Entity Item fires in BotStar, your agent runs Create Customer in Clockodo. 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 BotStar and Clockodo 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 BotStar can start in Clockodo
When New CMS Entity Item in BotStar
then Create Customer in Clockodo
When New CMS Entity Item in BotStar
then Create Project in Clockodo
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 BotStar and Clockodo
Triggers and actions 1 trigger · 47 actions
Trigger
New CMS Entity ItemTriggers when a new item is added to a CMS entity.
Action
Create Bot AttributeCreates a bot attribute (a bot-wide variable) on a bot.
Action
Create CMS Entity ItemCreates an item in a CMS entity.
Action
Create Custom User AttributeCreates a custom user attribute that every user of the bot can carry.
Action
Delete Bot AttributeDeletes a bot attribute from a bot.
Action
Delete CMS Entity ItemDeletes an item from a CMS entity.
Action
Get BotReturns one BotStar bot by its ID.
Action
Get CMS EntityReturns one CMS entity with its field definitions.
Action
Get CMS Entity ItemReturns one CMS entity item with its field values.
Action
Get UserReturns a bot user's profile, tags and custom attributes.
Action
List Bot AttributesReturns all bot attributes of a bot, with their names, types and values.
Action
List BotsReturns the bots in your BotStar account, each with its ID, name and team name.
Action
List CMS EntitiesReturns the CMS entities of a bot with their fields.
Action
List CMS Entity ItemsReturns the items of a CMS entity, optionally filtered by name or status.
Action
Publish BotPublishes a bot's draft changes to live.
Action
Send MessageSends a text message to a Facebook Messenger user of your bot.
Action
Update Bot AttributeUpdates a bot attribute's name, description or value.
Action
Update CMS Entity ItemUpdates an item in a CMS entity.
Action
Update User AttributesUpdates a bot user's standard and custom attributes.
Action
Create AbsenceCreates an absence (holiday, sick day, home office, overtime reduction and more) for a co-worker in Clockodo.
Action
Create CustomerCreates a new customer in Clockodo with its name, number, color, billing defaults and optional note.
Action
Create EntryCreates a time entry in Clockodo: a regular time entry for a customer and service, a lump-sum value entry, or a lump-sum service entry.
Action
Create ProjectCreates a new project for a customer in Clockodo, with optional number, note, dates, budget and service assignments. Returns the created project.
Action
Create ServiceCreates a new service in Clockodo that time entries can be booked against.
Action
Create SubprojectCreates a subproject under an existing project in Clockodo.
Action
Create UserCreates a new co-worker in your Clockodo account with their email, name and role, plus optional team, language, time settings and edit locks.
Action
Delete customerDeletes a customer from your Clockodo account.
Action
Delete entryDeletes a time entry from Clockodo.
Action
Delete projectDeletes a project in Clockodo. Optionally checks whether the project could be deleted without deleting it.
Action
Get customerReturns a single Clockodo customer by its id, including name, number, color, active status and billing defaults.
Action
Get entryReturns a single Clockodo time or lump-sum entry by its id, including customer, project, service, times, duration and billability.
Action
Get projectReturns a single Clockodo project by its id, including its customer, budget, completion status, dates and assigned services.
Action
Get userReturns a single Clockodo co-worker by id, including name, email, role, team, time zone and work settings.
Action
List absencesReturns the absences (holidays, sick days, home office and other leave) recorded in Clockodo, optionally filtered by year, co-worker, team, absence type or status.
Action
List customersReturns the customers in your Clockodo account, optionally filtered by active status or search text and sorted by name, id or status.
Action
List entriesReturns the time and lump-sum entries recorded in Clockodo between a start and end time, optionally filtered by co-worker, customer, project, service, billability or description.
Action
List projectsReturns the projects in your Clockodo account, optionally filtered by customer, active or completed status, or search text.
Action
List servicesReturns the services in your Clockodo account, optionally filtered by active status or search text.
Action
List usersReturns the co-workers in your Clockodo account, optionally filtered by active status, team or search text.
Action
Start clockStarts the Clockodo clock for a customer and service, creating a running time entry. Any clock already running for the user is stopped.
Action
Stop clockStops the running Clockodo clock entry and returns the stopped time entry, plus any new entry that was started in its place.
Action
Update AbsenceUpdates an existing absence (holiday, sick day, home office, etc.) in Clockodo, changing only the details you fill in. Returns the updated absence.
Action
Update CustomerUpdates an existing customer in Clockodo, changing only the details you fill in, and returns the updated customer.
Action
Update EntryUpdates an existing Clockodo time or lump-sum entry, changing only the details you fill in, and returns the updated entry.
Action
Update ProjectUpdates an existing project in Clockodo, changing only the details you fill in, and returns the updated project.
Action
Update ServiceUpdates an existing service in Clockodo, changing its name, number, note, billing id or active status. Fields left blank keep their current values.
Action
Update SubprojectUpdates an existing subproject in Clockodo, such as its name, budget, dates or assigned services. Fields left blank keep their current values.
Action
Update UserUpdates an existing co-worker in Clockodo, changing only the details you fill in.
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 BotStar
BotStar to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BotStar to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BotStar to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BotStar to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BotStar to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BotStar to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Clockodo
HubSpot to ClockodoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ClockodoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ClockodoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ClockodoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ClockodoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ClockodoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
BotStar and Clockodo, answered
What can start an automation from BotStar?
Any of BotStar's 1 trigger in the catalog, including New CMS Entity Item. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Clockodo when something happens in BotStar?
Any of Clockodo's 29 actions, including Create Absence, Create Customer, Create Entry and Create Project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clockodo to BotStar?
Clockodo has no triggers in the catalog today, so automations start in BotStar. If you need the other direction, ask: your agent reads Clockodo's API documentation and adds it.
Do I have to build a connector for BotStar or Clockodo?
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 BotStar and Clockodo 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.