ChMeetings and Parallel Integration

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

Automate the handoff between ChMeetings and Parallel - your productivity events flow into ai actions on a visual canvas your team can read. Set up the workflow once with 3 simple steps in the WEXTL® builder, let AI take smart decisions between apps, and never write a line of glue code again.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about ChMeetings and Parallel

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

  • Parallel

    • AI
    • 1 trigger
    • 17 searches
    • 19 actions

    Web search, page extraction and deep research for agents and workflows.[6]

How to connect ChMeetings to Parallel

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

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

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

Parallel modules

  • Add an Enrichment to a FindAll Run Extends the candidates of a FindAll run with extra data described by an Output Schema. Use Processor to choose the tier and MCP Servers to let the enrichment call outside servers.
  • Add Runs to a Task Group Queues several task runs in one batch from a JSON array of Inputs. Use Default Task Spec for runs without their own, and turn on Refresh Status to bring the group status up to date.
  • Cancel a FindAll Run Stops a FindAll run that is still searching and marks it as cancelled.
  • Cancel a Monitor Cancels a monitor and ends its checks on the set Frequency.
  • Clear Memory Empties a whole memory scope, removing everything stored under its Memory Scope Key.
  • Create a Chat Completion Answers a conversation sent as Messages, each with a Role and Content, from a Parallel Model. Use Previous Interaction ID to continue earlier context and Max Tokens to cap the reply length.
  • Create a FindAll Run Starts a search for entities matching an Objective, an Entity Type and Match Conditions. A heavier Generator searches more thoroughly. Use Exclude List to leave out entities you already know.
  • Create a FindAll Spec from an Objective Turns a plain-language Objective into a ready FindAll spec with an Entity Type, Match Conditions and a Generator. Review it before starting a run.
  • Create a Monitor Sets up a recurring watch on the web with a Type and a Frequency. Give a Query to follow a search, or a Task Run ID to follow a run, and add a Webhook URL to be called on events.
  • Create a Response Produces an answer to the text of Input, guided by optional Instructions. Use Reasoning Effort to set how much the model thinks and Previous Response ID to carry earlier context forward.
  • Create a Task Group Opens an empty container for batching task runs, optionally tagged with Metadata. The Taskgroup Id it gets is used by the other group modules.
  • Create a Task Run Researches a question or task given as Input with the chosen Processor. Heavier tiers dig deeper. Use Include Domains or Exclude Domains to restrict sources and Output Type to shape the answer.
  • Evict from Memory Removes one task run, monitor or FindAll run from memory, by its Kind and ID. Use Memory Scope Key to act on a specific scope.
  • Extend a FindAll Run Raises the target of an earlier FindAll run by the Additional Match Limit, so it keeps searching for more matches.
  • Extract Web Page Content Reads each web page from the list of URLs and returns excerpts. Add an Objective or Search Queries to focus them, Max Characters to bound their length, and turn on Full Content or Links for more.
  • Get a FindAll Run Checks how a FindAll run is going and shows its Status, Generator and Metadata.
  • Get a FindAll Run Result Downloads the Candidates found by a FindAll run along with the Run record itself.
  • Get a FindAll Run Schema Shows how a FindAll run was set up, from its Objective and Entity Type to Match Conditions and Enrichments.
  • Get a Monitor Looks up one monitor to see its Frequency, Processor, Webhook, Settings and when it last ran.
  • Get a Task Group Reads the Status and Metadata of a batch of task runs, for the Task Group ID that Create a Task Group gave you.
  • Get a Task Group Run Fetches one run that belongs to a group, using both the Task Group ID and the Run ID. Its Status tells you how far along it is.
  • Get a Task Run Polls a task run by Run ID to see its Status, its Processor and whether it is still active.
  • Get a Task Run Input Recalls what a task run was asked, returning its Input, Task Spec and Processor.
  • Get a Task Run Result Collects the Output of a task run. Use Wait Seconds, up to 600, to hold the call until the run finishes.
  • Get Monitor Stats Counts all monitors in the account as a Total, with a split by processor.
  • List Monitor Events Lists what a monitor has detected, each with Event Type, Event Date and Output. Use Event Group ID to stay with one execution and Include Completions to see runs without changes.
  • List Monitors Lists monitors with their Type, Status and Frequency, up to Limit. Without a Status filter only active monitors appear.
  • Make a Decision Answers up to 100 Questions about a State using researched evidence. Use Published After to ignore older sources and Include Excerpts to attach the supporting quotes to the Citations.
  • Make an API Call Sends a free-form request to the Parallel REST API, signed with your saved credential.
  • Retrieve Memories Searches stored memories. Use Query to narrow what is found, Kind and Since to filter by type and date, and Limit to hold the count between 1 and 25.
  • Search Entities Quickly locates entities of a given Entity Type that fit an Objective. Use Match Limit to set how many are returned, from 5 to 1000.
  • Search Images Finds pictures for one or more Search Queries. Use Objective to sharpen the ranking, Mode to trade speed against depth and Max Results to limit the haul.
  • Search Places Looks for businesses and venues matching a Query around a Location or a Latitude and Longitude. Turn on Open Now or set Max Distance (km) to narrow the hits.
  • Search Web Runs web searches for short Search Queries and returns Results with excerpts. Restrict sources with Include Domains, and bound excerpt size with Max Characters.
  • Trigger a Monitor Run Runs a monitor right now instead of waiting for its next scheduled check.
  • Update a Monitor Adjusts a monitor with a new Frequency, a deeper Processor or a revised Query. Use Include Domains to replace the domains it watches.
  • Watch Events Starts the workflow when Parallel posts a webhook event, with its Event Type, Timestamp and Data.

Explore alternative integrations

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

Automate ChMeetings and Parallel on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and Parallel.

How do I connect ChMeetings and Parallel?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Add an Enrichment to a FindAll Run" in Parallel. ChMeetings has 1 trigger (including Watch Events). Parallel has 36 actions (including Add an Enrichment to a FindAll Run, Add Runs to a Task Group, and Cancel a FindAll Run). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore ChMeetings and Parallel, or get started