ChMeetings and codeREADr Integration

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

Connect ChMeetings and codeREADr 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 ChMeetings and codeREADr

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

  • ChMeetings

    • Productivity
    • 1 trigger
    • 60 searches
    • 50 actions

    Church management software for people, giving, events, groups and communication.[5]

  • codeREADr

    • Productivity
    • 2 triggers
    • 11 searches
    • 31 actions

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

How to connect ChMeetings to codeREADr

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

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

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

ChMeetings triggerscodeREADr actions

ChMeetings modules

  • Watch Events Starts a workflow when ChMeetings sends an event, with its Event Name and Payload. Delivery takes 1 to 5 minutes and the same event can arrive more than once.
  • Add a Person to a Group Enrolls a person into a ChMeetings group. Use Organization on diocese accounts to act inside a church or a ministry.
  • Add a Person to an Organization Links a person record to one of the organizations in your account, by Person ID.
  • Add Family Members Adds people to an existing family household. Each entry of Members links one person to a Family Role.
  • Cancel a Check-In Undoes the check-in of a person at an event occurrence.
  • Cancel a Check-Out Undoes the check-out of a person at an event occurrence.
  • Change a Family Member Role Gives a person already in a family a different Family Role.
  • Check In a Person Records that someone arrived at an occurrence of an event. Use Occurred At for the arrival time. The result shows the Status and Check In Code.
  • Check Out a Person Records that someone left an event occurrence, with Occurred At for the departure time, and gives the Checked Out At time.
  • Close a Batch Closes a contribution batch. The result shows whether it Is Opened.
  • Create a Batch Opens a new contribution batch on a chosen Date so donations can be grouped in it.
  • Create a Contribution Records a donation with its Date, Payment Method and the Funds it goes to. Use Person ID, or First Name, Last Name, Email or Mobile, to credit the giver, and Batch ID to place it in a batch.
  • Create a Family Forms a household from the people listed under Members, each with a Family Role. The Family ID of the new family is returned.
  • Create a Follow-Up Schedules a follow-up for a person on a Date. Give Assignee IDs for who handles it, and Type, Action ID and Notes to describe it.
  • Create a Fund Adds a giving fund with a Name. Turn on Is Tax Deductible, Is Default or Allow For Online Giving to set how it behaves.
  • Create a Group Starts a group with a Name. Use Privacy to set who can see it, Join Request Option to control how people join, and Description to explain it.
  • Create a Note Saves a Note on the profile of a person in your church database.
  • Create a Payment Method Adds a payment method under a Name that contributions can use.
  • Create a Person Adds a person to your church database with a First Name and Last Name. Add Email, Mobile, Birth Date, Gender or address fields to fill in the profile.
  • Create a Post Publishes or drafts a post with a Title and Body. Use Status for draft or published, Visibility for the audience, and Notify Members to alert people.
  • Create a Webhook Subscribes a URL to the chosen Events. The result includes the Secret used to sign deliveries.
  • Delete a Batch Deletes a contribution batch from your giving records.
  • Delete a Contribution Removes one recorded donation from your giving records.
  • Delete a Family Deletes a family household record from your database.
  • Delete a Follow-Up Cancels a scheduled follow-up task by removing it.
  • Delete a Fund Deletes a giving fund. Set Move To Fund ID to carry its contributions over to another fund.
  • Delete a Group Removes a group from your ChMeetings database.
  • Delete a Note Removes a note that was saved against a member.
  • Delete a Payment Method Removes a payment method from the list used by donations. Set Move To Payment Method ID to reassign existing contributions.
  • Delete a Person Deletes a person from your church database.
  • Delete a Post Removes a post from your community feed.
  • Delete a Webhook Removes a webhook registration so ChMeetings sends nothing more to its URL.
  • Get a Batch Retrieves one contribution batch with its Number, Date and whether it Is Opened.
  • Get a Family Reads a family household and lists the Members that belong to it, along with the Family ID.
  • Get a Follow-Up Fetches one follow-up with its Person Name, Date and Start Time.
  • Get a Fund Shows a fund with its Name and whether it Is Tax Deductible or Allow For Online Giving.
  • Get a Group Looks up a group, including its Privacy and Join Request Option.
  • Get a Note Retrieves one note from a person profile, with its Created On and Updated On dates.
  • Get a Payee Looks up a payee with its Email and Address, and whether it Is 1099 Eligible.
  • Get a Payment Method Reads one payment method, returning its ID and Name for use in contributions.
  • Get a Person Reads a person record with the First Name, Last Name, Nick Name and Email on file.
  • Get a Post Reads a post with its Title, Body, Status and Visibility.
  • Get a Transaction Fetches one accounting transaction with its Amount, Account and Payee.
  • Get a Webhook Reads a webhook with its URL, Event Names and whether it Is Active.
  • Get an Account Reads one accounting account, with its Name, Number, Type and whether it Is Archived.
  • Get an Accounting Category Fetches one accounting category with its Name, Type and Parent Category ID.
  • Get an Accounting Fund Looks up a fund from the accounting side and shows its Balance and whether it Is Default.
  • Get an Attendance Summary Summarizes attendance for an event occurrence, together with its Statistics. The Groups attending are listed too.
  • Get an Event Reads one event with its Title, Start Date, Recurrence and Location.
  • Get an Occurrence Reads one dated occurrence of an event, with its Title, Start and End.

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

Automate ChMeetings and codeREADr on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and codeREADr.

How do I connect ChMeetings and codeREADr?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Add a Barcode Value" in codeREADr. ChMeetings has 1 trigger (including Watch Events). 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 ChMeetings trigger actions in codeREADr, and codeREADr in ChMeetings?

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 ChMeetings and codeREADr?

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

Does ChMeetings integrate with codeREADr in real time?

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

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

References

List of sources used to gather information about the ChMeetings and codeREADr integration.

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

Explore ChMeetings and codeREADr, or get started