Integration
Connect awork and Fluent Support
When New Client fires in awork, your agent runs Add Tag to Ticket in Fluent Support, or New Customer in Fluent Support 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 Fluent Support 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 Fluent Support can do together
From awork to Fluent Support
When New Client in awork
then Add Tag to Ticket in Fluent Support
From Fluent Support to 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 Fluent Support
Triggers and actions 10 triggers · 31 actions
- New Client
Fires when a new company/client is created in awork. Poll/webhook on companies resource creation event.
- New Project
Triggers when a new project is created.
- New Task
Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.
- New Time Entry
Triggers when a new time entry is created.
- Updated Client
Fires when an existing company/client is updated in awork. Poll/webhook on companies resource update event.
- Updated Project
Fires when a project is updated in the awork workspace.
- Updated Task
Triggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.
- Updated Time Entry
Triggers when a time entry is updated.
- Create Client
Creates a client (company) in awork and returns the created company.
- Create Project
Creates a new project.
- Create Project Task
Creates a task in an awork project.
- Create Time Entry
Creates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc.
- Delete Client
Deletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks.
- Delete Project
Deletes an awork project and its tasks, optionally deleting its time entries too.
- Delete Project Task
Deletes an awork task by id.
- Delete Time Entry
Deletes a time entry in awork.
- Find Project Tasks by criteria
Returns up to 100 tasks of a project that match the specified filter criteria.
- Find Time Entries by criteria
Returns up to 100 time entries in the workspace that match the specified filter criteria.
- Get Client by ID
Finds a client by id
- Get Project by ID
Finds a project by id
- Get Task by ID
Returns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values.
- Get Time Entry
Returns a single awork time entry by its id, including its task, project, user, type of work and breaks.
- Search Clients
Returns up to 100 clients (companies) whose name contains the specified text.
- Search Projects
Returns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter.
- Search Users by Email
Returns the awork users whose contact information includes the specified email address.
- Update Client
Updates an existing client (company) by ID. Fields left blank keep their current values.
- Update Project
Updates fields (name, status, workflow, etc) on an existing awork project.
- Update Project Task
Updates fields (name, status, assignee, due date, etc) on an existing awork task.
- Update Time Entry
Updates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags.
- New Customer
Triggers when a new customer is added in Fluent Support.
- New Ticket
Triggers when a new support ticket is created in Fluent Support.
- Add Tag to Ticket
Adds an existing tag to a Fluent Support ticket.
- Close Ticket
Closes a Fluent Support ticket.
- Create Customer
Creates a new customer in Fluent Support with their name, email, contact details and an optional note.
- Create Ticket
Creates a new support ticket in Fluent Support for an existing customer.
- Get Ticket
Returns a Fluent Support ticket with its customer, responses and details.
- List Customers
Returns the customers in your Fluent Support help desk, optionally filtered by a search term.
- List Tickets
Returns support tickets from Fluent Support, optionally matching a search term.
- Reopen Ticket
Reopens a closed Fluent Support ticket.
- Reply to Ticket
Adds an agent reply or internal note to a Fluent Support ticket, optionally closing the ticket.
- Update Ticket
Updates one property of a ticket — its priority, customer priority, assigned agent or product.
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 Fluent Support
NoteForms to Fluent SupportCreate beautiful forms to fill your Notion databases.
ActiveCampaign to Fluent SupportActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Fluent SupportOrganize anything with Airtable, a modern database created for everyone.
Asana to Fluent SupportAsana is a collaborative information manager for workspace.
ClickUp to Fluent SupportClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to Fluent SupportDiscord is an all-in-one voice and text chat for gamers.
Questions
awork and Fluent Support, 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 Fluent Support when something happens in awork?
Any of Fluent Support's 10 actions, including Create Customer, Create Ticket, Update Ticket and Add Tag to Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fluent Support to awork?
Yes. When something happens in Fluent Support, your agent can act in awork too. This page covers both directions: Fluent Support's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or Fluent Support?
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 Fluent Support 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.