Aboard Sign and eSignatures.com Integration

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

Align data between Aboard Sign and eSignatures.com to automate productivity workflows. Actions made in Aboard Sign integration can trigger sequences of multiple actions inside eSignatures.com app - automatically, without any line of code.

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

Learn about Aboard Sign and eSignatures.com

Detailed info you need to know about Aboard Sign and eSignatures.com integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Aboard Sign

    • Productivity
    • 3 searches
    • 4 actions

    Get a document signed by email, check where a signing stands, and verify a signed copy. Aboard Sign allows only a few signings per day from one address, and WEXTL calls from shared addresses, so the daily limit may be reached early.[5]

  • eSignatures.com

    • Productivity
    • 7 searches
    • 18 actions

    Send and manage electronic signature contracts and templates.[6]

How to connect Aboard Sign to eSignatures.com

Set up your Aboard Sign and eSignatures.com integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Aboard Sign and eSignatures.com work in WEXTL?

WEXTL exposes actions and triggers for Aboard Sign and eSignatures.com 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.

Aboard Sign actionseSignatures.com actions

Aboard Sign modules

  • Get a Signing Status Looks up an open signing by its Signing ID and reports who has signed and who is still awaited. A signing that is over returns the state gone instead of an error.
  • Get Log Entries Finds a document on the public log by its Fingerprint. A listed document means everyone signed, and an empty entries list means signatures are still missing.
  • Get the Public Key Fetches the key that countersigns every record, as a Key ID and a Public Key. It works without a site password, so a record can be checked outside the app.
  • Make an API Call Calls the Aboard Sign REST API directly with a free-form request, adding the site password when one is saved.
  • Start a Signing Mails every named person a link of their own to sign a document typed in as text. Needs a Sender Email and a Document, and the sender signs too.
  • Start a Signing from a File Sends an uploaded PDF, DOCX, RTF, Markdown or text file out for signature by email. Add up to four Signers besides the sender, and set a File Name when the mapped file has none.
  • Verify a Signed Copy Uploads a Signed PDF and checks every page, every signature and the seal. The answer holds a Verdict, a list of Problems and the Signers, and the vendor keeps nothing that is sent.

eSignatures.com modules

  • Add a Collaborator Invites a person to collaborate on a template. Add an Email to send them an invite and a Name for the collaborator. Returns the Template Collaborator Editor URL.
  • Add a Signer Adds a signer to an existing contract, using the Contract ID from Create a Contract. Use Mobile to add a phone number with country code, and Redirect URL to send the signer to a page after signing.
  • Create a Contract Creates a contract from a template, to be signed by the Signers it requires. Turn on Test for a demo contract with no fees, and Save As Draft to store it as a draft instead of sending it.
  • Create a Template Creates a template from Markdown content under a Title. Add Labels to group the template and its contracts, and the new Template ID is returned.
  • Delete a Signer Deletes a signer from the signer list of one contract.
  • Delete a Template Deletes a template from your eSignatures account.
  • Duplicate a Template Copies an existing template under a new Title. Use Placeholder Fields to replace placeholders in the copy, and Target Secret Token to give the copy to another account. The new Template ID is returned.
  • Generate a PDF Preview Creates a PDF preview for one contract, using the Contract ID saved from Create a Contract.
  • Get a Contract Shows the Status, Title, Signers and Contract PDF URL of one contract. Since eSignatures offers no contract list, copy the Contract ID from the create step.
  • Get a Template Fetches a template along with its Title, Created At, Placeholder Fields and Signer Field IDs.
  • Get Contract Content Reads the body of a contract as Markdown, returned beside its Contract ID.
  • Get Placeholder Fields Lists each placeholder field of one contract with its Placeholder Key and replacement values. Use Limit to cap the fields returned.
  • Get Template Content Reads the Markdown text of one template, returned next to its Template ID.
  • List Collaborators Returns the people collaborating on a template, each with a Name, Email and Template Collaborator Editor URL. Use Limit to restrict the number of people listed.
  • List Templates Returns your templates, each with its Template ID and Title. Use Limit to control how many templates are listed.
  • Make an API Call Runs a free-form request against the eSignatures.com REST API using your saved credential.
  • Remove a Collaborator Removes a collaborator from the people working on a template.
  • Resend a Sign Request Sends the signature request to a signer of a contract once more.
  • Send a Draft Sends a draft contract to its signers for signing, using the Contract ID given when the draft was created.
  • Update a Signer Edits the Name, Email, Mobile or Company Name of one contract signer. Use Signed Document Delivery Method to set how the signed document is delivered.
  • Update a Template Renames or relabels a template through its Title and Labels, the latter shared with the contracts made from it.
  • Update Contract Content Applies find-and-replace Edits to the Markdown text of a contract. Turn on Dry Run to try them without saving anything.
  • Update Placeholder Fields Sets new placeholder values on a contract through Replace With Text, Replace With Markdown or Replace With Template.
  • Update Template Content Runs find-and-replace Edits over the template Markdown. Use Dry Run to test the edits without saving.
  • Withdraw a Contract Withdraws a contract from signing in eSignatures, with its Contract ID mapped from Create a Contract.

Explore alternative integrations

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

Automate Aboard Sign and eSignatures.com on WEXTL®

Claim your 3-day trial to build Aboard Sign with eSignatures.com integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Aboard Sign and eSignatures.com.

How do I connect Aboard Sign and eSignatures.com?

Connect your Aboard Sign and eSignatures.com accounts once, pick an action 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 Aboard Sign and eSignatures.com?

Example: use the Aboard Sign "Get a Signing Status" action to perform the eSignatures.com "Add a Collaborator" action. Aboard Sign has 7 actions (including Get a Signing Status, Get Log Entries, and Get the Public Key). eSignatures.com has 25 actions (including Add a Collaborator, Add a Signer, and Create a Contract). Add filters and transforms between steps when you need them.[1]

Can I use a Aboard Sign action to perform a eSignatures.com action?

Yes. Pick an action in either app, then an action in the other, and map the fields between them.[2]

Do I need to write code to integrate Aboard Sign and eSignatures.com?

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

Does Aboard Sign integrate with eSignatures.com in real time?

Yes. Trigger-based automations start the moment Aboard Sign (or eSignatures.com) 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 Aboard Sign + eSignatures.com 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 Aboard Sign with eSignatures.com?

You can build your Aboard Sign + eSignatures.com automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Aboard Sign and eSignatures.com integration.

  1. Aboard Sign and eSignatures.com integration source code, module specs and credentials implementation.
  2. Our Aboard Sign and eSignatures.com integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Aboard Sign and eSignatures.com, 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. Aboard Sign integration information
  6. eSignatures.com integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Aboard Sign and eSignatures.com integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Aboard Sign and eSignatures.com, or get started