Docupilot and SignRequest Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Docupilot and SignRequest to automate productivity workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Docupilot and SignRequest

Detailed info you need to know about Docupilot and SignRequest integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Docupilot

    • Productivity
    • 2 triggers
    • 44 searches
    • 61 actions

    Document automation with templates, e-signatures and bulk generation.[5]

  • SignRequest

    • Productivity
    • 1 trigger
    • 17 searches
    • 13 actions

    Electronic signatures for teams, with templates and document signing.[6]

How to connect Docupilot to SignRequest

Set up your Docupilot and SignRequest integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Docupilot and SignRequest work in WEXTL?

WEXTL exposes actions and triggers for Docupilot and SignRequest that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Docupilot triggersSignRequest actions

Docupilot modules

  • Add Envelope Documents Adds more Documents to an e-signature envelope that already exists.
  • Append Files Joins PDF files into one, in the order given, with at least two required. Use Output File Name to name the joined file. The result has a File URL and a File Name.
  • Cancel a Bulk Task Cancels a bulk generation task of a template and returns the task with its Task ID and Errors.
  • Cancel an Envelope Cancels an e-signature envelope and records the Reason, which recipients can see.
  • Convert a File Converts a file reachable at a public link to another format. Give its File Type, such as docx, and use Output Type to choose PDF, PNG image or PNG images (zip). The result has a File URL and File Name.
  • Copy a Content Block Duplicates a content block, giving the copy its own Name and an API Name that differs from the original. Add a Description for a short note about the copy.
  • Copy a Template Duplicates a template under a fresh Title. Use Folder to file the copy elsewhere, since it lands in the home folder when empty.
  • Copy a Template From a Version Builds a new template from one version of an existing template and gives it a Title. Set Folder to store it somewhere other than the home folder.
  • Create a Content Block Creates a content block from an uploaded file, such as footer.docx, under a Name. Give it an API Name of letters, numbers and underscores, which templates use to include the block.
  • Create a Document Link Makes a link for generating a document from a template. The result has the Link ID and its Path.
  • Create a Folder Starts a folder for templates. The result shows its Folder ID and Created Time.
  • Create a History Export Starts an export of generated documents from From Date to To Date, both days included. You get back an Export ID.
  • Create a Template Builds a template out of a file with merge fields, such as a Word document, named by Title. Use Output Type to set the kind of file it produces and Folder to place it.
  • Create a Webhook Delivery Sets up a webhook delivery for a template, sending the generated document to the URL. Use Headers for something like an authorization header, and Data for extra JSON sent with the file.
  • Create an Email Delivery Sets up an email delivery that sends the generated document of a template to the addresses listed under To. Use Subject and Body with merge fields from the template, and CC, BCC or From Email to shape the message.
  • Create an Envelope Opens an e-signature envelope around the Documents to be signed. Use Folder ID to file it in a folder, or the default folder is used.
  • Create an Envelope Recipient Registers a recipient by Email on an envelope. Use Order to place the recipient in the signing sequence, which starts at 1.
  • Delete a Content Block Deletes a content block from the Docupilot workspace.
  • Delete a Delivery Removes one delivery configured on a template.
  • Delete a Delivery Attachment Removes one attached file from a delivery.
  • Delete a Document Link Deletes a link that generates documents from a template.
  • Delete a Folder Deletes a template folder. The templates inside move to the home folder.
  • Delete a Template Sends a template to the trash, from where it can be restored.
  • Delete a Template Permanently Removes a template that is already in the trash, with no way back.
  • Delete an Envelope Sends an envelope to the trash, from where it can be restored later.
  • Delete an Envelope Document Removes one of the files that belong to an envelope.
  • Delete an Envelope Permanently Deletes an envelope that is already in the trash, which cannot be undone.
  • Delete an Envelope Recipient Removes a signer from the recipient list of an envelope.
  • Download a Content Block File Fetches the file that makes up a content block. The result has the File, File Name and Size (Bytes).
  • Download a Delivery Attachment Pulls an attachment of a delivery, returning the File with its Content Type.
  • Download a Template File Saves the source file of a template. Use Version ID to fetch an older version, and leave it empty for the current one.
  • Download a Template Version File Reads back the stored file that belongs to one saved version of a template.
  • Download All Envelope Documents Downloads all the documents of an envelope in a single file. Set Include History to Yes to add the signing history.
  • Download an Envelope Attachment Fetches an attachment that a recipient added to an envelope, with its Content Type.
  • Download an Envelope Document Gets a single document from an envelope as a file, with its File Name and Size (Bytes).
  • Download Recipient Attachments Returns every file a certain recipient attached to an envelope, packed as a zip file.
  • Generate a Document Fills a template with your merge data and produces the document. Use Output Type to override the template output, Version to choose Latest or Live, and Data JSON for merge values as a JSON object. The result has a File URL and File Name.
  • Generate a Document File Returns the File itself rather than a link, along with its File Name and Size (Bytes), after filling a template with merge data. Generate a Document is the version that gives a File URL.
  • Get a Bulk Draft Fetches a bulk generation task while it is still a draft. The result lists its Rows, Row Count, Suggested Mapping and Delimiter.
  • Get a Bulk Mapping Reads the column mapping Docupilot suggests for a bulk draft. Use Delimiter to name the character that separates the CSV columns, such as a comma.
  • Get a Bulk Task Returns one bulk generation task with its Status, Total Rows, Successful Rows and Errors.
  • Get a Content Block Loads one content block with its Name, API Name, Content Block Type and Description.
  • Get a Content Block by Key Gets a content block by its API Name. The result has its Name, Content Block Type and Fields.
  • Get a Delivery Fetches one delivery of a template, including its Delivery Type, To, Subject and Attachments.
  • Get a Signing Link Returns the Signing Link, the address used to sign an envelope.
  • Get a Template Fetches one template with its Title, Description, Template Type and Status.
  • Get a Template Version Loads one version of a template, including its Name, Version Type, Created Time and whether it is Starred or Live.
  • Get Content Block Fields Shows which merge fields a content block expects, each with its Field Name, Field Type and Reference Type. Use Search to filter by field name.
  • Get Content Block Test Data Reads the test data saved on a content block, together with its Name and Description.
  • Get Envelope Counts Counts envelopes by status, giving Created, Pending, Voided, Declined and Completed.

SignRequest modules

  • Cancel a SignRequest Stops a signature request before signing is finished, and reports its Detail and Cancelled values.
  • Create a Document Builds a document out of a File from URL, File Contents with a File Name, or a Template. Use Events Callback URL to receive every event for the new document.
  • Create a Document Attachment Attaches a file to a Document, either through File from URL or through File Contents with a File Name. Documents made from a template take their attachments in the SignRequest UI.
  • Create a SignRequest Delivers a Document to the people listed under Signers for their signatures. Use Redirect URL to choose the page signers land on after signing, and Prepare Before Sending to prepare the document first.
  • Create a Team Registers a team called Name under a Subdomain, the part before .signrequest.com. Meant for SignRequest integration partners, since most teams are created in SignRequest itself.
  • Delete a Document Removes a document that SignRequest holds for you.
  • Delete a Team Deletes a team through the SignRequest API.
  • Forward a SignRequest Moves a signing task to a different email address, away from the current signer. Add a Forwarded Reason to explain the change, and everyone involved will see it.
  • Get a Document Reads a single document with its Status and download links. Links expire after five minutes, so check Processing to see whether the PDF is still catching up.
  • Get a Document Attachment Fetches one attachment of a document, showing its Name and File. The download link expires after five minutes.
  • Get a SignRequest Gets a signature request with its Signers, Subject and Message.
  • Get a Team Returns a team together with its Events Callback URL and Members.
  • Get a Team Member Shows the role of one team member, covering admin, active and owner status.
  • Get a Template Fetches a template and the signer placeholders it defines, together with its Name. The API cannot create templates, so they come from SignRequest.
  • Get an Event Looks up one recorded document event and shows its Event Type, Status and Timestamp.
  • Invite a Team Member Emails an invitation to join a Team. Turn on Admin to invite the person as an administrator, or Owner to make them an owner.
  • List API Tokens Shows the API tokens on this account with their Name and Key. Use Limit to set how many tokens are returned, and treat the result as secret.
  • List Audit Events Returns audit records such as Login failed, Login successful or a password reset request. Use Timestamp On or After and Timestamp Before to set a UTC date range, or User IP to follow one address.
  • List Document Attachments Finds the files attached to documents. Use Document to look at the attachments of one document only.
  • List Documents Returns documents in the account, narrowed with External ID, From Email or Status. Use Limit to set the maximum number of documents.
  • List Events Pulls events SignRequest recorded for documents. Use Document Status to filter on the status of the document rather than the event.
  • List SignRequests Retrieves signature requests. Use From Email to see only those sent from one sender address, or Who to filter on who was asked to sign.
  • List Team Members Lists the members of your SignRequest teams. Try User Email or User Last Name to look someone up.
  • List Teams Shows the teams in SignRequest, with each Subdomain and its Members.
  • List Templates Retrieves the templates created in SignRequest, along with their Signers. Use Limit to cap the number of templates.
  • Make an API Call Runs a free-form request against the SignRequest REST API using your saved credential.
  • Quick Create a SignRequest Makes a document and requests signatures for it in a single step. Provide Signers plus a File from URL, File Contents or Template.
  • Resend a SignRequest Email Sends the email of a signature request once more, with a Detail message in reply.
  • Search Documents Searches by Query, Name or Signer Emails to find documents. Use Autocomplete for a partial search term and Signer Data to get each signer as its own row.
  • Update a Team Updates a team by changing its Name, Phone or Primary Color. Use Events Callback URL to send every event for the team to one URL.
  • Watch SignRequest Events Runs the workflow as soon as SignRequest sends a webhook for an event, with its Event Type, Status, Document and Signer.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Docupilot and SignRequest integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Docupilot and SignRequest on WEXTL®

Claim your 3-day trial to build Docupilot with SignRequest integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Docupilot and SignRequest.

How do I connect Docupilot and SignRequest?

Connect your Docupilot and SignRequest accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Docupilot and SignRequest?

Example: when the "Watch Events (Instant)" trigger in Docupilot fires, WEXTL can "Cancel a SignRequest" in SignRequest. Docupilot has 2 triggers (including Watch Events (Instant) and Watch Generated Documents). SignRequest has 30 actions (including Cancel a SignRequest, Create a Document, and Create a Document Attachment). Add filters and transforms between steps when you need them.[1]

Can Docupilot trigger actions in SignRequest, and SignRequest in Docupilot?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Docupilot and SignRequest?

No. Docupilot-to-SignRequest automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Docupilot integrate with SignRequest in real time?

Yes. Trigger-based automations start the moment Docupilot (or SignRequest) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Docupilot + SignRequest integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Docupilot with SignRequest?

You can build your Docupilot + SignRequest automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Docupilot and SignRequest integration.

  1. Docupilot and SignRequest integration source code, module specs and credentials implementation.
  2. Our Docupilot and SignRequest integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Docupilot and SignRequest, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Docupilot integration information
  6. SignRequest integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Docupilot and SignRequest integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Docupilot and SignRequest, or get started