Integration
Connect Pipefile to Nutrient Document Web Services API
When File Request Created fires in Pipefile, your agent runs Convert Microsoft Office File to PDF in Nutrient Document Web Services API. 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 Pipefile and Nutrient Document Web Services API 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 Pipefile can start in Nutrient Document Web Services API
When File Request Created in Pipefile
then Convert Microsoft Office File to PDF in Nutrient Document Web Services API
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 Pipefile and Nutrient Document Web Services API
Triggers and actions 1 trigger · 17 actions
- File Request Created
Triggers when a file request is created.
- Add File Request From Template
Create 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.
- Create Contact
Add to contacts
- Delete Contact
Delete a contact by id. Returns 204 No Content on success.
- Get Contact
Retrieve one contact by id.
- Get File Request
Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.
- List Contacts
Retrieve a paginated list of contacts, filterable by name/email/phone partial match.
- List File Request Templates
Retrieve the list of file request templates available for creating new file requests, with optional name search.
- Search File Requests
Finds all file requests matching this search query (contact name, email, tags, etc).
- Send Request
Create and send a new request
- Update Contact
Update name/email/phone of an existing contact by id.
- Convert Doc/Docx to Image
Renders a Word document (DOC or DOCX) as an image (PNG, JPEG or WebP). A single rendered page returns one image; several pages return a ZIP archive of images.
- Convert Image to PDF
Converts an image (JPG, PNG, TIFF, WebP, GIF and more) into a PDF document.
- Convert Microsoft Office File to PDF
Converts a Word, Excel or PowerPoint file to a PDF document.
- Convert PDF to PDF/A
Converts a PDF into an archive-ready PDF/A document at the conformance level you choose.
- Extract Tables From PDF
Extracts the tables in a PDF and returns their rows and cells as structured data, page by page.
- Flatten PDF Annotations
Flattens the annotations and form fields of a PDF into the page content so they can no longer be edited, and returns the flattened PDF.
- Optimize PDF
Compresses and optimizes a PDF to reduce its file size, and returns the optimized PDF.
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 Pipefile
Pipefile to ChannelsChannels is a data-driven phone system that lets you make and take calls directly in the browser.
Pipefile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pipefile to StripeStripe is a payment processing platform for online businesses.
Pipefile to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pipefile to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Nutrient Document Web Services API
HubSpot to Nutrient Document Web Services APIHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Nutrient Document Web Services APIGoogle Sheets
Gmail to Nutrient Document Web Services APIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Nutrient Document Web Services APIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefile and Nutrient Document Web Services API, answered
What can start an automation from Pipefile?
Any of Pipefile's 1 trigger in the catalog, including File Request Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Nutrient Document Web Services API when something happens in Pipefile?
Any of Nutrient Document Web Services API's 7 actions, including Convert Doc/Docx to Image, Convert Image to PDF, Convert Microsoft Office File to PDF and Convert PDF to PDF/A. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Nutrient Document Web Services API to Pipefile?
Nutrient Document Web Services API has no triggers in the catalog today, so automations start in Pipefile. If you need the other direction, ask: your agent reads Nutrient Document Web Services API's API documentation and adds it.
Do I have to build a connector for Pipefile or Nutrient Document Web Services API?
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.