Integration
Connect Pyrus to Leave Dates
When New Form Task fires in Pyrus, your agent runs Add department in Leave Dates. 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 Pyrus and Leave Dates 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Pyrus can start in Leave Dates
When New Form Task in Pyrus
then Add department in Leave Dates
When New Form Task in Pyrus
then Add leave in Leave Dates
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 Pyrus and Leave Dates
Triggers and actions 1 trigger · 20 actions
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
Action
Add departmentCreates a new department in a Leave Dates company.
Action
Add leaveRequests a leave for one or more employees in a Leave Dates company, using the day breakdowns returned by a leave draft.
Action
Cancel leaveCancels a leave request in Leave Dates.
Action
Create EmployeeCreates a new employee in a Leave Dates company.
Action
Delete employeeDeletes an employee's employment record from a Leave Dates company.
Action
List departmentsReturns the departments of a Leave Dates company.
Action
List employeesReturns the employees of a Leave Dates company, optionally limited to one department.
Action
Update employeeUpdates an existing employee's details, such as name, email, department, approver and employment dates.
Action
Update leaveUpdates an existing leave request's dates, type, reason and day breakdown.
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 Pyrus
Pyrus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pyrus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pyrus to StripeStripe is a payment processing platform for online businesses.
Pyrus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pyrus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pyrus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Leave Dates
HubSpot to Leave DatesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Leave DatesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Leave DatesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Leave DatesGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Leave DatesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Leave DatesGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pyrus and Leave Dates, answered
What can start an automation from Pyrus?
Any of Pyrus's 1 trigger in the catalog, including New Form Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leave Dates when something happens in Pyrus?
Any of Leave Dates's 9 actions, including Create Employee, Update employee, Update leave and Add department. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leave Dates to Pyrus?
Leave Dates has no triggers in the catalog today, so automations start in Pyrus. If you need the other direction, ask: your agent reads Leave Dates's API documentation and adds it.
Do I have to build a connector for Pyrus or Leave Dates?
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 Pyrus and Leave Dates 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.