Aboard Sign and Carbone Integration

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

Keep Aboard Sign and Carbone matched by integrating their events and actions. When productivity events happen in Aboard Sign, update the Carbone automatically - without any line of code in visual workflow builder.

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

Learn about Aboard Sign and Carbone

Detailed info you need to know about Aboard Sign and Carbone 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]

  • Carbone

    • Productivity
    • 2 triggers
    • 6 searches
    • 8 actions

    Generate PDFs and other documents from templates and data, and convert files between formats.[6]

How to connect Aboard Sign to Carbone

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

How does the integration between Aboard Sign and Carbone work in WEXTL?

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

Carbone triggersAboard Sign actions

Carbone modules

  • Convert a Base64 Document Converts a Base64 File, or the text of Source Text, to the Output Format you need. Use Watermark Text to stamp every page of a PDF and PDF Password to lock it. Returns the File, File Name and Content Type.
  • Convert a Document Turns an uploaded File into another Output Format, such as PDF. Protect it with a PDF Password, stamp a Watermark Text, or merge values from Data. Returns the File with its Size (Bytes).
  • Delete a Template Deletes a stored template with all its versions, or just a single version of it.
  • Download a Generated Document Gets the file of a document rendered earlier, from the Render ID that Generate Document or Watch Rendered Documents reported. Carbone deletes the document after one download and after one hour. Turn on Download as Attachment to mark the file as a download.
  • Download a Template Retrieves the original file of a stored template, returning the File, File Name and Content Type.
  • Generate a Document Merges Data into a Template and renders the Output Format you need. Add a Webhook URL to render in the background, and Batch Split By to turn each item of a list into its own document. Use Document Name to name the file.
  • Generate and Download a Document Renders a Template with your Data and returns the finished file in one step. Use Language and Timezone to format numbers and dates, and Currency Source with Currency Target to convert amounts.
  • Get the API Status Checks that the Carbone service is reachable and reports its Version.
  • List Template Categories Returns the categories your templates are filed in. Use Limit to cap how many are read.
  • List Template Tags Returns the tags that appear on your templates, up to the Limit, for reuse when sorting others.
  • List Templates Lists stored templates. Use Search Text to match a name, comment or ID, narrow by Category, Origin, Template ID or Version ID, and set Include Versions to see the older versions of each template.
  • Make an API Call Calls the Carbone REST API directly with a free-form request under your saved credential.
  • Update Template Metadata Edits the details of a stored template: Name, Comment, Category or Tags. Plan a release with Deploy At or Delete At, or use Deploy Now to publish at once.
  • Upload a Template Stores a Template File in Carbone. Give it a Name and Comment, and use Versioning with Existing Template ID to add a version to a template already stored. Returns the ID and Version ID.
  • Watch New Templates Checks on a schedule for templates added or revised since the last run and emits each. Use Category to watch only one category, and Limit to set how many of the newest templates the first check takes.
  • Watch Rendered Documents Starts the workflow when Carbone finishes a render. Each event has the Render ID, Success flag and any Error.

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.

Explore alternative integrations

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

Automate Aboard Sign and Carbone on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Aboard Sign and Carbone.

How do I connect Aboard Sign and Carbone?

Connect your Aboard Sign and Carbone 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 Aboard Sign and Carbone?

Example: when the "Watch New Templates" trigger in Carbone fires, WEXTL can "Get a Signing Status" in Aboard Sign. Aboard Sign has 7 actions (including Get a Signing Status, Get Log Entries, and Get the Public Key). Carbone has 14 actions (including Convert a Base64 Document, Convert a Document, and Delete a Template). Add filters and transforms between steps when you need them.[1]

Can Aboard Sign trigger actions in Carbone, and Carbone in Aboard Sign?

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 Aboard Sign and Carbone?

No. Aboard Sign-to-Carbone 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 Carbone in real time?

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

You can build your Aboard Sign + Carbone 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 Carbone integration.

  1. Aboard Sign and Carbone integration source code, module specs and credentials implementation.
  2. Our Aboard Sign and Carbone integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Aboard Sign and Carbone, 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. Carbone 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 Carbone integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Aboard Sign and Carbone, or get started