Integration
Connect awork and Pipefile
When something happens in awork or Pipefile, your agent does the next thing in the other. Describe it 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 Pipefile 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 Pipefile can do together
From awork to Pipefile
When New Client in awork
then Add File Request From Template in Pipefile
When New Project in awork
then Create Contact in Pipefile
From Pipefile to awork
When File Request Created in Pipefile
then Create Client in awork
When File Request Created in Pipefile
then Create Project 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 Pipefile
Triggers and actions 9 triggers · 31 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
File Request CreatedTriggers when a file request is created.
Action
Add File Request From TemplateCreate a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
Action
Create ContactAdd to contacts
Action
Delete ContactDelete a contact by id. Returns 204 No Content on success.
Action
Get ContactRetrieve one contact by id.
Action
Get File RequestRetrieve detailed information about one file request by id, including contents, items, files, and tracking events.
Action
List ContactsRetrieve a paginated list of contacts, filterable by name/email/phone partial match.
Action
List File Request TemplatesRetrieve the list of file request templates available for creating new file requests, with optional name search.
Action
Search File RequestsFinds all file requests matching this search query (contact name, email, tags, etc).
Action
Send RequestCreate and send a new request
Action
Update ContactUpdate name/email/phone of an existing contact by id.
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 Pipefile
HubSpot to PipefileHubSpot is your all-in-one stop for all of your marketing software needs.
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Google Sheets to PipefileGoogle Sheets
Gmail to PipefileGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefileGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
awork and Pipefile, 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 Pipefile when something happens in awork?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to awork?
Yes. When something happens in Pipefile, your agent can act in awork too. This page covers both directions: Pipefile's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or Pipefile?
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.