Docupilot
HomeLoginSignup
  • Docupilot Help Documentation
  • Getting Started
  • Building Templates
    • Tokens (Merge Field)
    • Document Builder
    • AI-Powered Template Builder
    • Word Document (DOCX) & PowerPoint (PPTX)
    • Excel (XLSX)
    • Fillable PDF
    • Template Preferences
    • Formatting Your Data
    • Numerical Calculations
    • Advanced usage
  • Test your document template
  • Deliveries
    • Email
    • Webhook
    • Dropbox
    • Google Drive
    • One Drive
    • DropboxSign (formerly Hellosign)
    • DocuSign
    • SignNow
    • Xodo sign (formerly Eversign)
    • Signable
    • Yousign
    • Amazon S3
    • SFTP
  • Create document
    • Data Capture Form
    • API & Webhook Integration
    • Bulk Create
    • Integrate with Zapier
    • Integrate with Make
    • Integrate with Zoho Flow
    • Integrate with Integrately
  • Integrations
    • Google Forms
    • Google Sheets
    • Airtable Extension
    • Microsoft Word Add-In
  • Collaborating with multiple users
    • Invite users
    • Manage & delete users
  • Reports
  • Settings
    • Workspace
    • API Settings
    • Manage Subscription
    • Linked Accounts
  • Folders & Templates management
    • Manage Folders
    • Manage Templates
    • Share Templates & Folders
  • Profile & Account Security
  • Frequently Asked Questions (FAQs)
  • Developers
    • API Overview
    • Templates API
    • Folders API
  • Updates
    • Scheduled Downtime Notification
Powered by GitBook
On this page
  • Adding a DropboxSign Account
  • Configuration
  • Using Text Tags Field Parsing
  • Matching Signer
  • Optional Recipients

Was this helpful?

  1. Deliveries

DropboxSign (formerly Hellosign)

Send generated documents automatically for Signing.

PreviousOne DriveNextDocuSign

Last updated 12 months ago

Was this helpful?

To start with a DropboxSign (formerly Hellosign) delivery, choose the Dropboxsign (formerly Hellosign) option from the list of deliveries available in the Deliveries tab.

You need a DropboxSign API plan for HelloSign Delivery. Please refer

Adding a DropboxSign Account

Configuration

Title

The title you want to assign to the Signature Request.

Subject

The subject in the email that will be sent to the signers.

Message

The custom message in the email that will be sent to the signers.

Signers Name

The name of the signer.

Signers Email

The email address of the signer

CC

The email addresses that should be CCed.

Use Text Tags

Hide Text Tags

Sequenced Signing

Enable this if you wish to enable Sequenced Signing.

Using Text Tags Field Parsing

To enable Text Tags and make sure you enable Use Text Tags. Your Text Tags will be converted into UI components for the user to interact with. Keep in mind that by default the tags themselves will remain on the page. To hide the tags from the end user you can change the text color to match the background (such as white on white). Alternatively you can set Hide Text Tags although we don't recommend this because auto-removal can lead to unwanted clipping.

To begin and end a tag, use square brackets [ ] in your document. Within the square brackets, use the pipe character | to divide the parts of the tag. The first part of the tag is the type. The second part indicates if it is required or not. The third part indicates which signer in the list of signers needs to complete the field. The last two parts are optional and are for setting a label and unique ID.

For example: [text|noreq|signer1|Label|UniqueId]

Text Tags let you specify which signer the field is for, what type of field it is, and if the field is required or not in addition to the relative size of the field. The types of fields available are the same as when you create a template:

TEXT TAG VALUE

FIELD TYPE

text

Text field

check

Checkbox field

date

Date field

initial

Signer's initials field

sig

Signer's signature field

text-merge

A text field that has default text set by the api

checkbox-merge

A checkbox field that has default value set by the api

The only valid values for field requirement are "req" and "noreq". The value defaults to "req" if the entry is not understood.

Matching Signer

When you write a Text Tag you must assign it to somebody. The number N in "signerN" represents the signer index, For example with these two text tags:

  • [sig|req|signer1|OptionalLabel|OptionalID]

  • [initial|req|signer2|OptionalLabel|OptionalID]

You have specified that signer[1] is required to sign and signer[2] is required to initial.

If you text tags, you will need to configure the signers fields in the delivery configuration. The number of signers configured in the document using text tags must match the number of signers configured in the delivery.

Optional Recipients

Enabling optional recipients in the DropboxSign delivery will skip invalid signers and carbon copy (cc) entries.

You can find your API Key here

Enable this if you wish to enable parsing in your document

Enable this if you wish to enable automatic Text Tag removal. It is preferred that you don't enable this, hide your tags with white text or something similar because the automatic removal system can cause unwanted clipping. See the walkthrough for more details.

https://app.hellosign.com/home/myAccount#api
Text Tags
Text Tags
https://www.hellosign.com/api
Adding a new Dropbox Sign (formerly hellosign) delivery in Docupilot
Adding a new Dropbox sign account
Using DropboxSign Text Tags in Docupilot Template
Configuring Dropbox Sign delivery on Docupilot