--- title: "Connect Azure Service Bus to Clockodo - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Create Customer\" in Clockodo." canonical: "https://apiant.ai/connect/azure-service-bus-to-clockodo" --- # Connect Azure Service Bus to Clockodo When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Create Customer** in [Clockodo](https://apiant.ai/connections/clockodo). Describe the whole flow and it is built, tested on every scenario and kept running. Azure Service Bus **1** trigger Azure Service Bus **9** actions Clockodo **29** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Azure Service Bus and Clockodo to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Azure Service Bus can start in Clockodo - When **New Message in Queue** in Azure Service Bus then **Create Customer** in Clockodo - When **New Message in Queue** in Azure Service Bus 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 Azure Service Bus and Clockodo ## Triggers and actions 1 trigger · 38 actions - Trigger **New Message in Queue** Triggers when a message arrives in a Service Bus queue. Each check picks up the next message and removes it from the queue, so use a queue dedicated to this automation. - Action **Abandon Message** Abandons a message received with Receive Message (Peek-Lock), releasing its lock so it can be received again. - Action **Complete Message** Completes a message received with Receive Message (Peek-Lock), removing it from the queue. - Action **Create Queue** Creates a new queue in the connected Service Bus namespace and returns its settings. - Action **Delete Queue** Deletes a queue from the connected Service Bus namespace, along with all of its messages. - Action **Get Queue** Returns a Service Bus queue's settings and its current message counts. - Action **List Queues** Returns the queues in the connected Service Bus namespace, with each queue's status and message counts. - Action **Receive and Delete Message** Receives the next message from a queue in the connected Service Bus namespace and removes it from the queue. - Action **Receive Message (Peek-Lock)** Receives the next message from a queue and locks it, so another receiver cannot take it. Complete the message to remove it, or abandon it to release it back to the queue; the lock expires on its own after the queue's lock duration. - Action **Send Message to Queue** Sends a message to a queue in the connected Service Bus namespace, with optional subject, IDs, scheduling and custom properties. - Action **Create Absence** Creates an absence (holiday, sick day, home office, overtime reduction and more) for a co-worker in Clockodo. - Action **Create Customer** Creates a new customer in Clockodo with its name, number, color, billing defaults and optional note. - Action **Create Entry** Creates 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 Project** Creates a new project for a customer in Clockodo, with optional number, note, dates, budget and service assignments. Returns the created project. - Action **Create Service** Creates a new service in Clockodo that time entries can be booked against. - Action **Create Subproject** Creates a subproject under an existing project in Clockodo. - Action **Create User** Creates 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 customer** Deletes a customer from your Clockodo account. - Action **Delete entry** Deletes a time entry from Clockodo. - Action **Delete project** Deletes a project in Clockodo. Optionally checks whether the project could be deleted without deleting it. - Action **Get customer** Returns a single Clockodo customer by its id, including name, number, color, active status and billing defaults. - Action **Get entry** Returns a single Clockodo time or lump-sum entry by its id, including customer, project, service, times, duration and billability. - Action **Get project** Returns a single Clockodo project by its id, including its customer, budget, completion status, dates and assigned services. - Action **Get user** Returns a single Clockodo co-worker by id, including name, email, role, team, time zone and work settings. - Action **List absences** Returns 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 customers** Returns the customers in your Clockodo account, optionally filtered by active status or search text and sorted by name, id or status. - Action **List entries** Returns 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 projects** Returns the projects in your Clockodo account, optionally filtered by customer, active or completed status, or search text. - Action **List services** Returns the services in your Clockodo account, optionally filtered by active status or search text. - Action **List users** Returns the co-workers in your Clockodo account, optionally filtered by active status, team or search text. - Action **Start clock** Starts the Clockodo clock for a customer and service, creating a running time entry. Any clock already running for the user is stopped. - Action **Stop clock** Stops the running Clockodo clock entry and returns the stopped time entry, plus any new entry that was started in its place. - Action **Update Absence** Updates an existing absence (holiday, sick day, home office, etc.) in Clockodo, changing only the details you fill in. Returns the updated absence. - Action **Update Customer** Updates an existing customer in Clockodo, changing only the details you fill in, and returns the updated customer. - Action **Update Entry** Updates an existing Clockodo time or lump-sum entry, changing only the details you fill in, and returns the updated entry. - Action **Update Project** Updates an existing project in Clockodo, changing only the details you fill in, and returns the updated project. - Action **Update Service** Updates an existing service in Clockodo, changing its name, number, note, billing id or active status. Fields left blank keep their current values. - Action **Update Subproject** Updates an existing subproject in Clockodo, such as its name, budget, dates or assigned services. Fields left blank keep their current values. - Action **Update User** Updates an existing co-worker in Clockodo, changing only the details you fill in. ## Each app on its own - [ **Azure Service Bus** Managed message broker providing queues and pub/sub topics for reliable, asynchronous communication between...](https://apiant.ai/connections/azure-service-bus) - [ **Clockodo** Clockodo is a time tracking software for teams and individuals, helping you record work hours, manage...](https://apiant.ai/connections/clockodo) Reviews ## What our customers say ## More from Azure Service Bus - [ **Azure Service Bus to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/azure-service-bus-to-hubspot) - [ **Azure Service Bus to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/azure-service-bus-to-salesforce) - [ **Azure Service Bus to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/azure-service-bus-to-slack) - [ **Azure Service Bus to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/azure-service-bus-to-google-sheets) - [ **Azure Service Bus to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/azure-service-bus-to-gmail) - [ **Azure Service Bus to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/azure-service-bus-to-google-calendar) ## More into Clockodo - [ **HubSpot to Clockodo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-clockodo) - [ **Salesforce to Clockodo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-clockodo) - [ **Slack to Clockodo** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-clockodo) - [ **Google Sheets to Clockodo** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-clockodo) - [ **Gmail to Clockodo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-clockodo) - [ **Google Calendar to Clockodo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-clockodo) Questions ## Azure Service Bus and Clockodo, answered ### ### What can start an automation from Azure Service Bus? Any of Azure Service Bus's 1 trigger in the catalog, including New Message in Queue. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Clockodo when something happens in Azure Service Bus? 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 Azure Service Bus? Clockodo has no triggers in the catalog today, so automations start in Azure Service Bus. 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 Azure Service Bus 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 Azure Service Bus 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.