Integration
Connect awork and Reply
When New Client fires in awork, your agent runs Add contact list in Reply, or New Email Opened in Reply 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 Reply to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Reply can do together
From awork to Reply
When New Client in awork
then Add contact list in Reply
When New Project in awork
then Add note to contact in Reply
From Reply to awork
When New Email Opened in Reply
then Create Project Task in awork
When New Emails Sent in Reply
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 Reply
Triggers and actions 15 triggers · 37 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
Inbox Category Set for ReplyTriggers when an email reply in Reply is given an inbox category, automatically or by a user.
Trigger
New Email OpenedTriggers when a contact opens a tracked email sent from Reply.
Trigger
New Emails SentTriggers when Reply sends an email from a sequence step.
Trigger
New Link ClickedTriggers when a recipient clicks a tracked link in an email sent from Reply.
Trigger
New Person BounceTriggers when an email sent from Reply bounces or is rejected by the recipient's mail server.
Trigger
New Person Opt OutTriggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).
Trigger
Prospect FinishedTriggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.
Action
Add contact listCreates a new contact list in Reply, optionally shared with your team.
Action
Add note to contactAdds a note to a contact's timeline in Reply.
Action
Add sequenceCreates a new sequence in Reply with its steps, schedule, sending accounts and settings.
Action
Create\Update PersonCreates a Reply contact, or updates the existing contact with the same email address.
Action
Delete contactDeletes a contact from your Reply account.
Action
Find contacts by criteriaReturns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.
Action
Get contactReturns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.
Action
Get sequenceReturns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.
Action
List contact listsReturns the contact lists you own plus those shared with your team, optionally filtered by name.
Action
List contactsReturns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.
Action
List inbox categoriesReturns the inbox categories you can file conversations under.
Action
List Sequence ContactsReturns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.
Action
List sequencesReturns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.
Action
Mark as FinishedMarks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.
Action
Remove Person From CampaignRemoves a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.
Action
Send Test Webhook EventSends a test event from an existing Reply webhook subscription to its configured URL.
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 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...
awork to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Reply
HubSpot to ReplyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ReplyGoogle Sheets
Gmail to ReplyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ReplyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ReplyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ReplyMailchimp marketing automation and email platform.
Questions
awork and Reply, 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 Reply when something happens in awork?
Any of Reply's 16 actions, including Create\Update Person, Send Test Webhook Event, Add contact list and Add note to contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Reply to awork?
Yes. When something happens in Reply, your agent can act in awork too. This page covers both directions: Reply's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or Reply?
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.
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.