Carbone and codeREADr Integration

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

Keep Carbone and codeREADr matched by integrating their events and actions. When productivity events happen in Carbone, update the codeREADr 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 Carbone and codeREADr

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

  • codeREADr

    • Productivity
    • 2 triggers
    • 11 searches
    • 31 actions

    Barcode scanning services, validation databases, users, devices and scan records.[6]

How to connect Carbone to codeREADr

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

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

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

codeREADr modules

  • Add a Barcode Value Registers a barcode Value in a database. Set the Response the scanner shows, mark it Valid or not, and turn on Trim Value to strip surrounding spaces.
  • Add a Scan Property Stamps a custom property on one or more scans. Both the property Name and its Value are case-sensitive, at most 100 characters each.
  • Add an Answer Option Adds the Answer text as a choice on a multiple choice, dropdown or checkbox question. The question ID is returned.
  • Add Many Barcode Values Adds or updates between 1 and 100 values in one call. Each row can name its own Database. Turn on Trim Values to remove extra spaces around each one.
  • Add or Update a Barcode Value Saves a barcode Value to a database and overwrites it when it already exists. Add a Response for the scanner to show, or set Valid.
  • Add Questions to a Service Attaches data collection Questions to Services. Use Show to set when each question appears and Required Questions to make answers mandatory.
  • Add Users to a Service Authorizes Users to scan with the chosen Services. Use all for either to cover every user or service.
  • Create a Database Makes a database of valid barcode values under a Name. Choose Case Sensitive carefully, because it cannot be changed afterwards.
  • Create a Question Writes a data collection question from its Question text. Use Type for short answer, numbers only or a barcode button, while other types need answer options added later.
  • Create a Service Sets up a scanning service. Pick a Validation Method to record or validate scans online or on-device, and supply a Database for the two validating kinds.
  • Create a User Registers a scanning user from a Username. An email address as the username sends an invitation, otherwise set a Password. Use Device Limit to cap how many devices activate.
  • Delete a Barcode Value Deletes one barcode from a database, but only when it matches what is stored.
  • Delete a Database Removes a database, unless a service still uses it. This cannot be undone.
  • Delete a Question Removes a data collection question. This cannot be undone.
  • Delete a Scan Property Deletes the property called Name from a scan.
  • Delete a Service Removes a service from your scanning account. This cannot be undone.
  • Delete a User Deletes a scanning user. This cannot be undone.
  • Delete All Database Values Empties a database of every value it holds. This cannot be undone.
  • Delete an Answer Option Deletes one answer choice from a question, which must keep at least two options.
  • Delete Scans Deletes scans from your account, one ID or a comma-separated list at a time. This cannot be undone.
  • Generate a Barcode Renders a barcode for a Value of up to 500 characters, returning the File with its Filename and Content Type. Size, text and frame options adjust the look.
  • Get a Scan Property Reads the Value of the property called Name on one scan.
  • Get API Limits Shows how many API calls you may make per Minute and per Day, and how many are left.
  • List Database Values Reads the values stored in a database along with their Response and Validity. Narrow by exact Value, Value Contains or Response Contains, and page through with Offset.
  • List Databases Shows your databases with their ID, Name and Count. Set Detail to include the services that use each one.
  • List Devices Lists your scanning devices with their Devicename, Udid and Created date.
  • List Questions Retrieves your data collection questions with their Text, Type and Answers.
  • List Scan Uploads Lists uploads of on-device scans with their Status and Count. Filter by Services, Devices or Users.
  • List Scans Searches received scans. Filter by Keyword, Services, Devices, Users, Result, Value and Value Contains, or between From and To dates.
  • List Services Reads your scanning services with the ID, Name, Validationmethod, Postback and Database of each. Use Services to read only some of them.
  • List Users Lists scanning users with their Username, the Services they can use and their Limit.
  • Make an API Call Runs a free-form request against the codeREADr REST API using your saved credential.
  • Remove Questions from a Service Detaches data collection Questions from Services. Enter all in either field to cover every one.
  • Remove Users from a Service Revokes the permission of Users to scan on chosen Services.
  • Update a Barcode Value Changes the Response or Valid setting of a value held in one database. The value to edit must match the stored text exactly.
  • Update a Database Name Renames a barcode database. The new Name replaces the current one.
  • Update a Device Gives a scanning device a new Name.
  • Update a Question Changes the text of a question and sets an External ID of your own. The type cannot be changed.
  • Update a Service Reworks the Name, Description, Database, Postback URL and Duplicate Scans of a service. Set Active From and Active Until to give it a time window.
  • Update a User Edits the Username, Password or Device Limit for a scanning user. A Device Limit of 0 removes the cap.
  • Upload a CSV to a Database Imports the rows of a CSV File as barcode values. Turn on Trim Values to strip spaces and Import In The Background to defer the work.
  • Validate a User Tests a Username together with a Password against your scanning users and returns the ID, Services and Limit of the match.
  • Watch Scans Checks for scans received since the last check and emits each one. Use Service to follow one service and Limit to set how many the first check emits.
  • Watch Scans (Instant) Starts the workflow the moment a service posts a scan. The event includes the Value, Service ID, Device ID and Status.

Explore alternative integrations

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

Automate Carbone and codeREADr on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Carbone and codeREADr.

How do I connect Carbone and codeREADr?

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

Example: when the "Watch New Templates" trigger in Carbone fires, WEXTL can "Add a Barcode Value" in codeREADr. Carbone has 2 triggers (including Watch New Templates and Watch Rendered Documents). codeREADr has 42 actions (including Add a Barcode Value, Add a Scan Property, and Add an Answer Option). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Carbone and codeREADr, or get started