Integration
Connect awork and Jitbit Helpdesk
When New Client fires in awork, your agent runs Add tag to ticket in Jitbit Helpdesk, or New Ticket in Jitbit Helpdesk to Create Project Task in awork. 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 awork and Jitbit Helpdesk 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 awork and Jitbit Helpdesk can do together
From awork to Jitbit Helpdesk
When New Client in awork
then Add tag to ticket in Jitbit Helpdesk
When New Project in awork
then Create Ticket in Jitbit Helpdesk
From Jitbit Helpdesk to awork
When New Ticket in Jitbit Helpdesk
then Create Project Task in awork
When New Ticket in Jitbit Helpdesk
then Update Project Task in awork
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 awork and Jitbit Helpdesk
Triggers and actions 9 triggers · 40 actions
Trigger
New ClientFires when a new company/client is created in awork. Poll/webhook on companies resource creation event.
Trigger
New ProjectTriggers when a new project is created.
Trigger
New TaskTriggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.
Trigger
New Time EntryTriggers when a new time entry is created.
Trigger
Updated ClientFires when an existing company/client is updated in awork. Poll/webhook on companies resource update event.
Trigger
Updated ProjectFires when a project is updated in the awork workspace.
Trigger
Updated TaskTriggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.
Trigger
Updated Time EntryTriggers when a time entry is updated.
Action
Create ClientCreates a client (company) in awork and returns the created company.
Action
Create ProjectCreates a new project.
Action
Create Project TaskCreates a task in an awork project.
Action
Create Time EntryCreates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc.
Action
Delete ClientDeletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks.
Action
Delete ProjectDeletes an awork project and its tasks, optionally deleting its time entries too.
Action
Delete Project TaskDeletes an awork task by id.
Action
Delete Time EntryDeletes a time entry in awork.
Action
Find Project Tasks by criteriaReturns up to 100 tasks of a project that match the specified filter criteria.
Action
Find Time Entries by criteriaReturns up to 100 time entries in the workspace that match the specified filter criteria.
Action
Get Client by IDFinds a client by id
Action
Get Project by IDFinds a project by id
Action
Get Task by IDReturns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values.
Action
Get Time EntryReturns a single awork time entry by its id, including its task, project, user, type of work and breaks.
Action
Search ClientsReturns up to 100 clients (companies) whose name contains the specified text.
Action
Search ProjectsReturns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter.
Action
Search Users by EmailReturns the awork users whose contact information includes the specified email address.
Action
Update ClientUpdates an existing client (company) by ID. Fields left blank keep their current values.
Action
Update ProjectUpdates fields (name, status, workflow, etc) on an existing awork project.
Action
Update Project TaskUpdates fields (name, status, assignee, due date, etc) on an existing awork task.
Action
Update Time EntryUpdates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags.
Trigger
New TicketTriggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.
Action
Add articleCreates a new knowledge base article in a category.
Action
Add assetCreates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.
Action
Add companyCreates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.
Action
Add tag to ticketAdds a tag to a ticket. The tag is created if it does not already exist.
Action
Add time spentLogs a time spent entry on a ticket under the connected user. Requires technician permissions.
Action
Create New ReplyPosts a new reply (comment) to an existing helpdesk ticket.
Action
Create TicketCreates a new helpdesk ticket in a category, with a subject, body and priority.
Action
Create UserCreates a new helpdesk user. Requires administrator permissions.
Action
Find TicketSearches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.
Action
Find UserFinds a helpdesk user by their email address and returns their profile.
Action
Get ArticleReturns a knowledge base article with its full content, category, tags and attachments.
Action
Get ticketReturns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.
Action
List CompaniesReturns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.
Action
List Ticket CommentsReturns all comments (replies) posted on a Jitbit Helpdesk ticket.
Action
List ticketsReturns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.
Action
List Time Spent EntriesReturns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.
Action
Update companyUpdates a company's name, notes and email domains in Jitbit Helpdesk.
Action
Update ticketUpdates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.
Action
Update userUpdates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.
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 awork
awork to agiliteLow-code platform providing BPM, business rules, roles, and API-key managed services for workflow automation.
awork to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
awork to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
awork to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
awork to Google SheetsGoogle Sheets
awork to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Jitbit Helpdesk
HubSpot to Jitbit HelpdeskHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Jitbit HelpdeskGoogle Sheets
Gmail to Jitbit HelpdeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Jitbit HelpdeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Jitbit HelpdeskGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to Jitbit HelpdeskActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
awork and Jitbit Helpdesk, answered
What can start an automation from awork?
Any of awork's 8 triggers in the catalog, including New Client, New Project, New Task and New Time Entry. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Jitbit Helpdesk when something happens in awork?
Any of Jitbit Helpdesk's 19 actions, including Create New Reply, Create Ticket, Create User and Update company. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jitbit Helpdesk to awork?
Yes. When something happens in Jitbit Helpdesk, your agent can act in awork too. This page covers both directions: Jitbit Helpdesk's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or Jitbit Helpdesk?
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 awork and Jitbit Helpdesk 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.