ChMeetings and eSignatures.com Integration

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

Connect ChMeetings and eSignatures.com 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 eSignatures.com

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

  • eSignatures.com

    • Productivity
    • 7 searches
    • 18 actions

    Send and manage electronic signature contracts and templates.[6]

How to connect ChMeetings to eSignatures.com

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

How does the integration between ChMeetings and eSignatures.com work in WEXTL?

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

eSignatures.com modules

  • Add a Collaborator Invites a person to collaborate on a template. Add an Email to send them an invite and a Name for the collaborator. Returns the Template Collaborator Editor URL.
  • Add a Signer Adds a signer to an existing contract, using the Contract ID from Create a Contract. Use Mobile to add a phone number with country code, and Redirect URL to send the signer to a page after signing.
  • Create a Contract Creates a contract from a template, to be signed by the Signers it requires. Turn on Test for a demo contract with no fees, and Save As Draft to store it as a draft instead of sending it.
  • Create a Template Creates a template from Markdown content under a Title. Add Labels to group the template and its contracts, and the new Template ID is returned.
  • Delete a Signer Deletes a signer from the signer list of one contract.
  • Delete a Template Deletes a template from your eSignatures account.
  • Duplicate a Template Copies an existing template under a new Title. Use Placeholder Fields to replace placeholders in the copy, and Target Secret Token to give the copy to another account. The new Template ID is returned.
  • Generate a PDF Preview Creates a PDF preview for one contract, using the Contract ID saved from Create a Contract.
  • Get a Contract Shows the Status, Title, Signers and Contract PDF URL of one contract. Since eSignatures offers no contract list, copy the Contract ID from the create step.
  • Get a Template Fetches a template along with its Title, Created At, Placeholder Fields and Signer Field IDs.
  • Get Contract Content Reads the body of a contract as Markdown, returned beside its Contract ID.
  • Get Placeholder Fields Lists each placeholder field of one contract with its Placeholder Key and replacement values. Use Limit to cap the fields returned.
  • Get Template Content Reads the Markdown text of one template, returned next to its Template ID.
  • List Collaborators Returns the people collaborating on a template, each with a Name, Email and Template Collaborator Editor URL. Use Limit to restrict the number of people listed.
  • List Templates Returns your templates, each with its Template ID and Title. Use Limit to control how many templates are listed.
  • Make an API Call Runs a free-form request against the eSignatures.com REST API using your saved credential.
  • Remove a Collaborator Removes a collaborator from the people working on a template.
  • Resend a Sign Request Sends the signature request to a signer of a contract once more.
  • Send a Draft Sends a draft contract to its signers for signing, using the Contract ID given when the draft was created.
  • Update a Signer Edits the Name, Email, Mobile or Company Name of one contract signer. Use Signed Document Delivery Method to set how the signed document is delivered.
  • Update a Template Renames or relabels a template through its Title and Labels, the latter shared with the contracts made from it.
  • Update Contract Content Applies find-and-replace Edits to the Markdown text of a contract. Turn on Dry Run to try them without saving anything.
  • Update Placeholder Fields Sets new placeholder values on a contract through Replace With Text, Replace With Markdown or Replace With Template.
  • Update Template Content Runs find-and-replace Edits over the template Markdown. Use Dry Run to test the edits without saving.
  • Withdraw a Contract Withdraws a contract from signing in eSignatures, with its Contract ID mapped from Create a Contract.

Explore alternative integrations

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

Automate ChMeetings and eSignatures.com on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and eSignatures.com.

How do I connect ChMeetings and eSignatures.com?

Connect your ChMeetings and eSignatures.com 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 eSignatures.com?

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Add a Collaborator" in eSignatures.com. ChMeetings has 1 trigger (including Watch Events). eSignatures.com has 25 actions (including Add a Collaborator, Add a Signer, and Create a Contract). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore ChMeetings and eSignatures.com, or get started