Carbone and SignRequest Integration

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

Connect Carbone 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 Carbone and SignRequest

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

  • Carbone

    • Productivity
    • 2 triggers
    • 6 searches
    • 8 actions

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

  • SignRequest

    • Productivity
    • 1 trigger
    • 17 searches
    • 13 actions

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

How to connect Carbone to SignRequest

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

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

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

Carbone triggersSignRequest 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.

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 Carbone and SignRequest integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Carbone and SignRequest on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Carbone and SignRequest.

How do I connect Carbone and SignRequest?

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

Example: when the "Watch New Templates" trigger in Carbone fires, WEXTL can "Cancel a SignRequest" in SignRequest. Carbone has 2 triggers (including Watch New Templates and Watch Rendered 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 Carbone trigger actions in SignRequest, and SignRequest in Carbone?

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 Carbone and SignRequest?

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

Does Carbone integrate with SignRequest in real time?

Yes. Trigger-based automations start the moment Carbone (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 Carbone + 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 Carbone with SignRequest?

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

References

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

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

Explore Carbone and SignRequest, or get started