---
title: "Connect Pipefile to SignRequest - APIANT.ai"
description: "When \"File Request Created\" fires in Pipefile, your agent runs \"Add document\" in SignRequest."
canonical: "https://apiant.ai/connect/pipefile-to-signrequest"
---

# Connect Pipefile to SignRequest

When **File Request Created** fires in [Pipefile](https://apiant.ai/connections/pipefile), your agent runs **Add document** in [SignRequest](https://apiant.ai/connections/signrequest). Describe the whole flow and it is built, tested on every scenario and kept running.

Pipefile **1** trigger Pipefile **10** actions SignRequest **12** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Pipefile and SignRequest to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Pipefile can start in SignRequest

- When **File Request Created** in Pipefile then **Add document** in SignRequest
- When **File Request Created** in Pipefile then **Add document attachment** in SignRequest

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 SignRequest

## Triggers and actions 1 trigger · 22 actions

- Trigger

**File Request Created**

Triggers when a file request is created.

- Action

**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.

- Action

**Create Contact**

Add to contacts

- Action

**Delete Contact**

Delete a contact by id. Returns 204 No Content on success.

- Action

**Get Contact**

Retrieve one contact by id.

- Action

**Get File Request**

Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.

- Action

**List Contacts**

Retrieve a paginated list of contacts, filterable by name/email/phone partial match.

- Action

**List File Request Templates**

Retrieve the list of file request templates available for creating new file requests, with optional name search.

- Action

**Search File Requests**

Finds all file requests matching this search query (contact name, email, tags, etc).

- Action

**Send Request**

Create and send a new request

- Action

**Update Contact**

Update name/email/phone of an existing contact by id.

- Action

**Add document**

Creates a document in SignRequest from a file link, uploaded file content or a template, ready to be sent out for signature.

- Action

**Add document attachment**

Attaches a file to an existing SignRequest document, from a public link or from the file's contents.

- Action

**Cancel SignRequest**

Cancels a SignRequest that is still pending, so its signers can no longer sign the document.

- Action

**Delete document**

Deletes a document from your SignRequest team.

- Action

**Get document**

Returns a single SignRequest document by its ID, including its status, signers, and temporary links to the original and signed PDFs.

- Action

**Get SignRequest**

Returns a SignRequest by its ID, including its signers and their signing status, the email subject and message, and the linked document.

- Action

**List documents**

Returns the documents in your SignRequest team, optionally filtered by status, external ID, sender, owner or date.

- Action

**List SignRequests**

Returns the signature requests in your SignRequest team, optionally filtered by sender email or by who signs.

- Action

**List templates**

Returns the templates available to your SignRequest team, with each template's name, ID and signer setup.

- Action

**Resend SignRequest**

Resends the signature request email to the signers of an existing SignRequest who have not yet signed.

- Action

**Send SignRequest**

Sends an existing SignRequest document out for signature to one or more signers, and returns the new SignRequest.

- Action

**Send SignRequest From Template**

Creates a document from one of your SignRequest templates and sends it to the signers you choose in a single step. Returns the new SignRequest with its signers and document.

## Each app on its own

- [ **Pipefile** Pipefile streamlines the collection of personal, financial, and otherwise sensitive documents to keep your...](https://apiant.ai/connections/pipefile)
- [ **SignRequest** SignRequest is an electronic (digital) signature solution to get documents signed.](https://apiant.ai/connections/signrequest)

Reviews

## What our customers say

## More from Pipefile

- [ **Pipefile to Channels** Channels is a data-driven phone system that lets you make and take calls directly in the browser.](https://apiant.ai/connect/pipefile-to-channels)
- [ **Pipefile to Cleanvoice** API that removes filler words, silences, background noise, and mouth sounds from audio and video recordings.](https://apiant.ai/connect/pipefile-to-cleanvoice)
- [ **Pipefile to DeBounce** DeBounce is an email verification service that allows you to validate your email addresses and remove...](https://apiant.ai/connect/pipefile-to-debounce)
- [ **Pipefile to Disify** Disify checks email addresses for disposable and temporary providers.](https://apiant.ai/connect/pipefile-to-disify)
- [ **Pipefile to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefile-to-salesforce)
- [ **Pipefile to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pipefile-to-slack)

## More into SignRequest

- [ **HubSpot to SignRequest** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signrequest)
- [ **Salesforce to SignRequest** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signrequest)
- [ **Slack to SignRequest** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signrequest)
- [ **Google Sheets to SignRequest** Google Sheets](https://apiant.ai/connect/google-sheets-to-signrequest)
- [ **Gmail to SignRequest** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signrequest)
- [ **Google Calendar to SignRequest** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signrequest)

Questions

## Pipefile and SignRequest, 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 SignRequest when something happens in Pipefile?

Any of SignRequest's 12 actions, including Send SignRequest, Send SignRequest From Template, Add document and Add document attachment. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from SignRequest to Pipefile?

SignRequest has no triggers in the catalog today, so automations start in Pipefile. If you need the other direction, ask: your agent reads SignRequest's API documentation and adds it.

###

### Do I have to build a connector for Pipefile or SignRequest?

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 Pipefile and SignRequest 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.
