ChMeetings and KoBoToolbox Integration

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

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

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

  • KoBoToolbox

    • Productivity
    • 1 trigger
    • 59 searches
    • 52 actions

    Manage KoBoToolbox projects, submissions, exports, hooks, and organizations.[6]

How to connect ChMeetings to KoBoToolbox

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

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

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

KoBoToolbox modules

  • Add a Submission Adds a submission to a form. Use Form ID for the form identifier string rather than the project UID, and fill Submission with the answers for that form.
  • Assign a Permission Assigns a permission to a user. Extra JSON values can be supplied with Body fields.
  • Assign Permissions (Bulk) Assigns permissions for a project in bulk. Use Body fields to describe all of them as JSON.
  • Clone Permission Assignments Clones permission assignments onto a project. Add more JSON with Body fields when the call needs it.
  • Create a Hook Makes a hook in a project, with a Name and an Endpoint. Set Active to enable it, and set Payload template, Export type, Auth level or Email notification for the rest.
  • Create a Paired Data Connection Sets up a paired data connection with a project. Use Body fields to add the JSON for the connection.
  • Create a Project Creates a project from a Name and an Asset type. Use Clone from with the UID of an asset to copy it, and Settings to add project settings.
  • Create a Project File Uploads a file to a project. Use Body fields to describe the file with JSON values.
  • Create a Project History Export Begins an export of project history. More JSON values can be added with Body fields.
  • Create an Asset Snapshot Creates an asset snapshot in KoboToolbox. Use Body fields to define it with JSON.
  • Create an Asset Subscription Subscribes your account to an asset. Set Body fields to send further JSON to KoboToolbox.
  • Create an Export Setting Saves an export setting in a project. Use Body fields to send the options as JSON.
  • Create an Export Task Starts an export task for a project. Use Body fields for any more JSON the call needs.
  • Create an Organization Invite Invites someone to an organization. Use Body fields to fill in the invite as JSON.
  • Create My Access Log Export Requests an export of your access log. Pass extra JSON values to KoboToolbox with Body fields.
  • Delete a Hook Deletes a hook configured on a project.
  • Delete a Paired Data Connection Deletes a paired data connection that a project has in KoboToolbox.
  • Delete a Project Deletes a whole project from KoboToolbox.
  • Delete a Project File Deletes a stored project file from KoboToolbox.
  • Delete a Submission Removes a project submission from KoboToolbox.
  • Delete a Submission Validation Status Deletes the validation status that a submission carries in KoboToolbox.
  • Delete an Asset Snapshot Removes an asset snapshot from KoboToolbox.
  • Delete an Asset Subscription Cancels an asset subscription on your account.
  • Delete an Attachment Removes an attachment that belongs to a project in KoboToolbox.
  • Delete an Export Setting Removes the saved export setting of a project.
  • Delete an Export Task Deletes an export task stored under a project.
  • Delete an Organization Invite Removes an invite from an organization on the server.
  • Delete Submission Validation Statuses (Bulk) Removes validation statuses in bulk from submissions of a project.
  • Delete Submissions (Bulk) Deletes a group of submissions in a single request.
  • Deploy a Project Deploys a project. Turn on Active to make the deployment active.
  • Duplicate a Submission Duplicates a project submission. Use Body fields to add extra JSON values to the copy.
  • Get a Hook Returns a hook together with its details from KoboToolbox.
  • Get a Hook Log Reads a log entry written for a hook. UID Log comes from List Hook Logs.
  • Get a Paired Data Connection Gets a paired data connection set up for a project, as KoboToolbox holds it.
  • Get a Permission Assignment Fetches a permission assignment recorded for a project in KoboToolbox, with its details.
  • Get a Project Shows a project in KoboToolbox together with the details it holds.
  • Get a Project Deployment Looks up the deployment state that KoboToolbox reports for a project.
  • Get a Project File Fetches one file stored in a project. List Project Files shows the files available.
  • Get a Project Version Gets a version of a project from KoboToolbox. Versions are labelled by deployment date.
  • Get a Submission Reads a project submission in KoboToolbox, together with its answers.
  • Get a Submission Attachment Retrieves an attachment of a submission. Use UID Data for the submission and Id for the attachment.
  • Get a Submission Edit URL Returns the URL where a submission can be edited in KoboToolbox, as a link.
  • Get a Submission Validation Status Gets the validation status that KoboToolbox has recorded for a submission in a given project.
  • Get a User Looks up a KoboToolbox user and the account details held on the server.
  • Get an Asset Snapshot Reads the details of one asset snapshot stored on the KoboToolbox server.
  • Get an Asset Subscription Looks up one asset subscription held by your account on the server.
  • Get an Attachment Audio Duration Gets the audio duration of attachments in a project. Use Body fields to describe the request as JSON.
  • Get an Export Setting Fetches the saved export setting of a project with its details.
  • Get an Export Task Retrieves an export task that belongs to a project, with its details.
  • Get an Import Reads an import held on the server, such as an XLSForm file import.

Explore alternative integrations

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

Automate ChMeetings and KoBoToolbox on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and KoBoToolbox.

How do I connect ChMeetings and KoBoToolbox?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Add a Submission" in KoBoToolbox. ChMeetings has 1 trigger (including Watch Events). KoBoToolbox has 111 actions (including Add a Submission, Assign a Permission, and Assign Permissions (Bulk)). Add filters and transforms between steps when you need them.[1]

Can ChMeetings trigger actions in KoBoToolbox, and KoBoToolbox 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 KoBoToolbox?

No. ChMeetings-to-KoBoToolbox 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 KoBoToolbox in real time?

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

You can build your ChMeetings + KoBoToolbox 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 KoBoToolbox integration.

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

Explore ChMeetings and KoBoToolbox, or get started