ChMeetings and Grain Integration

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

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

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

  • Grain

    • Productivity
    • 1 trigger
    • 12 searches
    • 13 actions

    Meeting recordings, with transcripts, uploads, and hooks.[6]

How to connect ChMeetings to Grain

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

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

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

Grain modules

  • Add a Tag to a Recording Marks a Grain recording with a tag. Use Tag to set the text, in letters, numbers and dashes.
  • Create a Hook Registers an https endpoint that Grain posts to when an event happens, such as a recording being added or a story updated. Grain only accepts a Hook URL that answers with a 2xx. Use Include to add extra data to the post.
  • Create an Upload Starts a video, audio or transcript upload in Grain, depending on Media type. Set Auto promote to No to leave the upload staged. For a transcript, each segment has a Speaker key, Start, End and Text.
  • Delete a Hook Deletes a hook registered in Grain.
  • Download a Recording Downloads the video or audio file belonging to one Grain recording.
  • Get a Recording Returns a Grain recording with its Title, Source, Share state, Participants and Duration ms. Use Include to have Grain add extra data to it.
  • Get a Recording Transcript Pulls the transcript of a recording segment by segment, each with a Start, End, Text, Speaker and Participant id. Use Limit to restrict the number of segments.
  • Get a Recording Transcript as Text Exports a recording transcript as a plain file. Use Format to receive it as Txt, Vtt or Srt.
  • Get an Upload Pulls one upload with its Media type, Title, Status and Auto promote setting, plus its Recording id. Use Include to ask Grain for extra data.
  • Get the Token Info Shows the Type, Scope, User id, Workspace id, Name and Expires at of the access token behind your Grain connection.
  • List Hooks Shows the hooks set up in Grain, each with its Hook url, Hook type and whether it is Enabled. Use Filter to narrow them down.
  • List Meeting Types Fetches the meeting types known to Grain, giving the Name, Scope and Id of each. Use Limit to shorten the result.
  • List Recordings Finds recordings with their Title, Source, Share state, Tags and Participants. Narrow the result with Filter, add data with Include, or resume from an earlier page with Cursor.
  • List Teams Returns the teams Grain reports, each with its Id and Name. Set Limit to stop after the first few.
  • List Uploads Retrieves uploads along with Media type, Title, Status and Recording id. Pass a Cursor to pick up where an earlier run stopped, or a Filter to narrow the uploads.
  • List Users Gets users from Grain, each with a Name, Email and Id. Reduce the output with Limit.
  • Make an API Call Makes an authorized free-form request to the Grain REST API with your saved credential.
  • Promote an Upload Moves a staged upload on to become a recording. It applies to uploads created with Auto promote left off. Use Include to attach extra data to the result.
  • Remove a Tag from a Recording Strips a tag from a Grain recording. Use Tag to say which tag to remove, with the same letters, numbers and dashes it was added with.
  • Share a Recording with a Team Lets every member of a Grain team see a recording.
  • Share a Recording with a User Lets one person see a recording in Grain.
  • Unshare a Recording from a Team Withdraws the access that a Grain team had to a recording.
  • Unshare a Recording from a User Withdraws the access that one person had to a Grain recording.
  • Update a Recording Renames a recording by giving it a new Title.
  • Update an Upload Edits an upload that is awaiting or staged with Auto promote left off. Use Attributes to set the Title, Start datetime, Team or Recorders, or to supply transcript segments with a Speaker key, Start, End and Text.
  • Watch New Recordings Starts the workflow the moment Grain reports a new recording. Output includes the Type of event, the User id and the Data.

Explore alternative integrations

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

Automate ChMeetings and Grain on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and Grain.

How do I connect ChMeetings and Grain?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Add a Tag to a Recording" in Grain. ChMeetings has 1 trigger (including Watch Events). Grain has 25 actions (including Add a Tag to a Recording, Create a Hook, and Create an Upload). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore ChMeetings and Grain, or get started