ChMeetings and SignRequest Integration

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

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

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

  • SignRequest

    • Productivity
    • 1 trigger
    • 17 searches
    • 13 actions

    Electronic signatures for teams, with templates and document signing.[6]

How to connect ChMeetings to SignRequest

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

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

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

SignRequest modules

  • Cancel a SignRequest Stops a signature request before signing is finished, and reports its Detail and Cancelled values.
  • Create a Document Builds a document out of a File from URL, File Contents with a File Name, or a Template. Use Events Callback URL to receive every event for the new document.
  • Create a Document Attachment Attaches a file to a Document, either through File from URL or through File Contents with a File Name. Documents made from a template take their attachments in the SignRequest UI.
  • Create a SignRequest Delivers a Document to the people listed under Signers for their signatures. Use Redirect URL to choose the page signers land on after signing, and Prepare Before Sending to prepare the document first.
  • Create a Team Registers a team called Name under a Subdomain, the part before .signrequest.com. Meant for SignRequest integration partners, since most teams are created in SignRequest itself.
  • Delete a Document Removes a document that SignRequest holds for you.
  • Delete a Team Deletes a team through the SignRequest API.
  • Forward a SignRequest Moves a signing task to a different email address, away from the current signer. Add a Forwarded Reason to explain the change, and everyone involved will see it.
  • Get a Document Reads a single document with its Status and download links. Links expire after five minutes, so check Processing to see whether the PDF is still catching up.
  • Get a Document Attachment Fetches one attachment of a document, showing its Name and File. The download link expires after five minutes.
  • Get a SignRequest Gets a signature request with its Signers, Subject and Message.
  • Get a Team Returns a team together with its Events Callback URL and Members.
  • Get a Team Member Shows the role of one team member, covering admin, active and owner status.
  • Get a Template Fetches a template and the signer placeholders it defines, together with its Name. The API cannot create templates, so they come from SignRequest.
  • Get an Event Looks up one recorded document event and shows its Event Type, Status and Timestamp.
  • Invite a Team Member Emails an invitation to join a Team. Turn on Admin to invite the person as an administrator, or Owner to make them an owner.
  • List API Tokens Shows the API tokens on this account with their Name and Key. Use Limit to set how many tokens are returned, and treat the result as secret.
  • List Audit Events Returns audit records such as Login failed, Login successful or a password reset request. Use Timestamp On or After and Timestamp Before to set a UTC date range, or User IP to follow one address.
  • List Document Attachments Finds the files attached to documents. Use Document to look at the attachments of one document only.
  • List Documents Returns documents in the account, narrowed with External ID, From Email or Status. Use Limit to set the maximum number of documents.
  • List Events Pulls events SignRequest recorded for documents. Use Document Status to filter on the status of the document rather than the event.
  • List SignRequests Retrieves signature requests. Use From Email to see only those sent from one sender address, or Who to filter on who was asked to sign.
  • List Team Members Lists the members of your SignRequest teams. Try User Email or User Last Name to look someone up.
  • List Teams Shows the teams in SignRequest, with each Subdomain and its Members.
  • List Templates Retrieves the templates created in SignRequest, along with their Signers. Use Limit to cap the number of templates.
  • Make an API Call Runs a free-form request against the SignRequest REST API using your saved credential.
  • Quick Create a SignRequest Makes a document and requests signatures for it in a single step. Provide Signers plus a File from URL, File Contents or Template.
  • Resend a SignRequest Email Sends the email of a signature request once more, with a Detail message in reply.
  • Search Documents Searches by Query, Name or Signer Emails to find documents. Use Autocomplete for a partial search term and Signer Data to get each signer as its own row.
  • Update a Team Updates a team by changing its Name, Phone or Primary Color. Use Events Callback URL to send every event for the team to one URL.
  • Watch SignRequest Events Runs the workflow as soon as SignRequest sends a webhook for an event, with its Event Type, Status, Document and Signer.

Explore alternative integrations

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

Automate ChMeetings and SignRequest on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and SignRequest.

How do I connect ChMeetings and SignRequest?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Cancel a SignRequest" in SignRequest. ChMeetings has 1 trigger (including Watch Events). SignRequest has 30 actions (including Cancel a SignRequest, Create a Document, and Create a Document Attachment). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore ChMeetings and SignRequest, or get started