Carbone and Form.io Integration

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

Build productivity workflows between Carbone and Form.io on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

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

Learn about Carbone and Form.io

Detailed info you need to know about Carbone and Form.io 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]

  • Form.io

    • Productivity
    • 3 triggers
    • 43 searches
    • 49 actions

    Enterprise form and data management platform for building forms, collecting submissions, and managing projects.[6]

How to connect Carbone to Form.io

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

How does the integration between Carbone and Form.io work in WEXTL?

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

Form.io modules

  • Accept a Team Invite Accepts an invitation to join a Form.io team, sending the Body fields with the request.
  • Add a Team Member Puts another user on a Form.io team. Use Body to describe the member being added.
  • Check Whether a Submission Exists Calls the exists check on the submissions of a form in a Form.io project.
  • Create a Form Builds a new form inside a project from a Title, a Name and a Path. Add Components to lay out its fields as a Form.io component tree, and Type to set its type.
  • Create a Form Action Attaches an action to a form under a Name. Add a Title to label it, and Handler, Method, Priority and Settings to configure it.
  • Create a Platform User Registers a new Form.io platform account that signs in with an Email and a Password.
  • Create a Project Starts a Form.io project from a Title, with a Name that works as its alias.
  • Create a Project Admin Registers an administrator record on a project, with its fields passed through Body.
  • Create a Project Version Saves a tag for a project. The tag fields are sent through Body.
  • Create a Role Defines a role for a project from a Title, with an optional Role value.
  • Create a Stage Creates a stage under a Parent project, from a Title, a Name and a Type.
  • Create a Submission Records one set of answers on a form. Use Submission Data to pass an object whose keys are the form component keys.
  • Create a Team Creates a Form.io team from the Team data payload, such as its name.
  • Create a Tenant Adds a tenant below a Parent project, defined through its Title, Name and Type.
  • Delete a Blob (Azure) Deletes a blob that a form keeps in Azure storage.
  • Delete a File (Google Drive) Removes a file that a form keeps in Google Drive storage.
  • Delete a File (S3) Deletes a file kept in S3 storage for a form.
  • Delete a Form Removes a form definition from a Form.io project.
  • Delete a Form Action Deletes an action attached to a form of your Form.io project.
  • Delete a Project Deletes a Form.io project from the platform.
  • Delete a Project Admin Removes one administrator record from a project.
  • Delete a Project Version Removes a tag that belongs to a project.
  • Delete a Role Deletes a role defined in a project.
  • Delete a Stage Deletes a stage out of Form.io.
  • Delete a Submission Removes a stored submission from a form.
  • Delete a Team Removes a team from Form.io.
  • Delete a Tenant Deletes a tenant of the Form.io platform.
  • Delete an Uploaded PDF Removes a PDF file that was uploaded to a project.
  • Deploy a Version to a Stage Deploys a project version to a stage, with the deployment details sent through Body.
  • Export a Form Definition Calls the export endpoint of a form to get its definition from a Form.io project.
  • Export a Project Exports a Form.io project as a template, using the project export endpoint.
  • Generate a PDF From a Submission Renders a stored submission as a PDF document through the PDF proxy.
  • Get a Download File (Dropbox) Fetches the download response for a form upload on Dropbox.
  • Get a Download File (Google Drive) Fetches the download details for a form upload stored on Google Drive.
  • Get a Download SAS URL (Azure) Issues a shared access signature URL for downloading a form upload from Azure.
  • Get a Download URL (S3) Returns the address where a form upload in S3 can be downloaded.
  • Get a Form Loads the definition of a form, including its components.
  • Get a Form Action Reads a single action that is attached to a form in a Form.io project.
  • Get a Form Draft Shows the unpublished working copy of a form.
  • Get a Form Revision Pulls up one saved revision that belongs to a form in a Form.io project.
  • Get a PDF Download Token Requests a token that authorizes PDF downloads from one of your Form.io projects.
  • Get a PDF File Fetches an uploaded PDF from the PDF proxy, requesting the .pdf file itself.
  • Get a Project Reads one Form.io project from the platform.
  • Get a Project Admin Looks up a single administrator record that belongs to a Form.io project.
  • Get a Project Version Loads a single tag stored on a Form.io project.
  • Get a Role Fetches one role that a project defines, as it is stored in Form.io.
  • Get a Stage Remote Token Requests the remote access token that is issued for a stage in your account.
  • Get a Submission Loads one stored answer set from a form, using Form path and Submission ID.
  • Get a Submission PDF Download Returns the PDF rendition of a submission, for the Pdf Form ID and the Submission ID.
  • Get a Submission Revision Looks up a submission of a form by Form path and Submission ID, to read the stored record.

Explore alternative integrations

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

Automate Carbone and Form.io on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Carbone and Form.io.

How do I connect Carbone and Form.io?

Connect your Carbone and Form.io 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 Form.io?

Example: when the "Watch New Templates" trigger in Carbone fires, WEXTL can "Accept a Team Invite" in Form.io. Carbone has 2 triggers (including Watch New Templates and Watch Rendered Documents). Form.io has 92 actions (including Accept a Team Invite, Add a Team Member, and Check Whether a Submission Exists). Add filters and transforms between steps when you need them.[1]

Can Carbone trigger actions in Form.io, and Form.io 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 Form.io?

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

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

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

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

Explore Carbone and Form.io, or get started