Integration
Connect iLovePDF and Pyrus
When New Completed Task fires in iLovePDF, your agent runs Get Task in Pyrus, or New Form Task in Pyrus to Send Reminder in iLovePDF. 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 iLovePDF and Pyrus 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 iLovePDF and Pyrus can do together
From iLovePDF to Pyrus
When New Completed Task in iLovePDF
then Get Task in Pyrus
When New Completed Task in iLovePDF
then Add Task Comment in Pyrus
From Pyrus to iLovePDF
When New Form Task in Pyrus
then Send Reminder in iLovePDF
When New Form Task in Pyrus
then Send Signature Request in iLovePDF
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 iLovePDF and Pyrus
Triggers and actions 2 triggers · 13 actions
Trigger
New Completed TaskTriggers when an iLovePDF task (compress, merge, split, OCR and the other tools) finishes successfully, optionally only for one tool.
Action
Send ReminderSends a reminder email to every signer of a signature request who has not signed yet.
Action
Send Signature RequestSends a PDF from a public URL to a signer by email for a legally binding e-signature.
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.
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 iLovePDF
iLovePDF to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
iLovePDF to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
iLovePDF to MailchimpMailchimp marketing automation and email platform.
iLovePDF to StripeStripe is a payment processing platform for online businesses.
iLovePDF to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
iLovePDF to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Pyrus
HubSpot to PyrusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PyrusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PyrusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PyrusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PyrusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PyrusMailchimp marketing automation and email platform.
Questions
iLovePDF and Pyrus, answered
What can start an automation from iLovePDF?
Any of iLovePDF's 1 trigger in the catalog, including New Completed Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pyrus when something happens in iLovePDF?
Any of Pyrus's 11 actions, including Add Member, Add Task Comment, Find Catalog Items and Find Form Tasks. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pyrus to iLovePDF?
Yes. When something happens in Pyrus, your agent can act in iLovePDF too. This page covers both directions: Pyrus's triggers and iLovePDF's actions are listed here as well.
Do I have to build a connector for iLovePDF or Pyrus?
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 iLovePDF and Pyrus 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.