--- title: "Connect Azure Service Bus and WebWork Time Tracker - APIANT.ai" description: "When \"New Message in Queue\" fires in Azure Service Bus, your agent runs \"Update Task\" in WebWork Time Tracker." canonical: "https://apiant.ai/connect/azure-service-bus-to-webwork-time-tracker" --- # Connect Azure Service Bus and WebWork Time Tracker When **New Message in Queue** fires in [Azure Service Bus](https://apiant.ai/connections/azure-service-bus), your agent runs **Update Task** in [WebWork Time Tracker](https://apiant.ai/connections/webwork-time-tracker), or **New Contract** in WebWork Time Tracker to **Send Message to Queue** in Azure Service Bus. 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 WebWork Time Tracker **4** triggers WebWork Time Tracker **8** 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 WebWork Time Tracker 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 and WebWork Time Tracker can do together ### From Azure Service Bus to WebWork Time Tracker - When **New Message in Queue** in Azure Service Bus then **Update Task** in WebWork Time Tracker - When **New Message in Queue** in Azure Service Bus then **Get Task** in WebWork Time Tracker ### From WebWork Time Tracker to Azure Service Bus - When **New Contract** in WebWork Time Tracker then **Send Message to Queue** in Azure Service Bus - When **New Member** in WebWork Time Tracker then **Abandon Message** in Azure Service Bus 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 WebWork Time Tracker ## Triggers and actions 5 triggers · 17 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. - Trigger **New Contract** Fires once for each new contract (a member assigned to a project) in the selected WebWork workspace. - Trigger **New Member** Fires when a new member appears in a WebWork workspace. - Trigger **New Project** Fires once for each new project in the selected workspace. - Trigger **New Task** Fires once for each new task created in a WebWork project. - Action **Create Contract** Assign a member to a project in a WebWork workspace by creating a contract, with optional weekly hours limit, screenshot mode and hourly rate. - Action **Create Project** Create a new project in a WebWork workspace. Only workspace Owners and Executive Managers can create projects. - Action **Get Contract** Returns one contract (a member's assignment to a project) with its weekly hours limit, rate and status. - Action **Get Project** Returns one project by its ID, including its name, dates, estimate, notes and custom field values. - Action **Get Task** Returns one task with its title, status, priority and dates. - Action **Update Contract** Updates an existing contract (a member's assignment to a project): weekly hours limit, screenshot mode, hourly rate or status. - Action **Update Project** Updates an existing project by ID. Only the fields you fill in are changed. - Action **Update Task** Update an existing task in a WebWork project. Only the fields you fill in are changed. ## 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) - [ **WebWork Time Tracker** WebWork Time Tracker is a time and productivity tracking platform that lets you log hours, manage tasks, and...](https://apiant.ai/connections/webwork-time-tracker) 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 WebWork Time Tracker - [ **HubSpot to WebWork Time Tracker** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-webwork-time-tracker) - [ **Salesforce to WebWork Time Tracker** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-webwork-time-tracker) - [ **Slack to WebWork Time Tracker** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-webwork-time-tracker) - [ **Google Sheets to WebWork Time Tracker** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-webwork-time-tracker) - [ **Gmail to WebWork Time Tracker** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-webwork-time-tracker) - [ **Google Calendar to WebWork Time Tracker** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-webwork-time-tracker) Questions ## Azure Service Bus and WebWork Time Tracker, 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 WebWork Time Tracker when something happens in Azure Service Bus? Any of WebWork Time Tracker's 8 actions, including Create Contract, Create Project, Update Contract and Update Project. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from WebWork Time Tracker to Azure Service Bus? Yes. When something happens in WebWork Time Tracker, your agent can act in Azure Service Bus too. This page covers both directions: WebWork Time Tracker's triggers and Azure Service Bus's actions are listed here as well. ### ### Do I have to build a connector for Azure Service Bus or WebWork Time Tracker? 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 WebWork Time Tracker 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.