ChMeetings and Form.io Integration

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

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

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

  • 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 ChMeetings to Form.io

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

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

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

ChMeetings triggersForm.io 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.

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

Automate ChMeetings and Form.io on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and Form.io.

How do I connect ChMeetings and Form.io?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Accept a Team Invite" in Form.io. ChMeetings has 1 trigger (including Watch Events). 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 ChMeetings trigger actions in Form.io, and Form.io 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 Form.io?

No. ChMeetings-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 ChMeetings integrate with Form.io in real time?

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

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

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

Explore ChMeetings and Form.io, or get started