ChMeetings and DocuSeal Integration

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

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

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

  • DocuSeal

    • Productivity
    • 11 triggers
    • 7 searches
    • 17 actions

    Send, sign, and manage documents with DocuSeal e-signatures.[6]

How to connect ChMeetings to DocuSeal

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

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

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

DocuSeal modules

  • Archive a Submission Archives a DocuSeal submission. The result shows the ID and the time it was archived.
  • Archive a Template Archives a template and returns its ID with the Archived At time.
  • Clone a Template Makes a copy of an existing template. Leave Name empty to reuse the original name with (Clone) appended, and use Folder or External ID to file the copy.
  • Create a Submission Sends a template out for signature, naming each signer under Submitters with their Role and Email. Use Signing Order to send requests one at a time or all together, and Expires At to close the request after a deadline.
  • Create a Submission From DOCX Takes DOCX files from Documents and issues a signature request for them. Fill Dynamic Variables to replace the variable tags written inside the file.
  • Create a Submission From HTML Turns HTML content into a document and sends it to the signers listed under Submitters. Each item of Documents carries its own HTML plus an optional HTML Header and HTML Footer.
  • Create a Submission From PDF Uploads PDF files and starts a signature request over them. Use Combine With Templates to add existing templates to the same submission, or Merge Into One PDF to join the files.
  • Create a Template From DOCX Builds a reusable template from DOCX files. Use Folder to file it and Enable Shared Link to give it a shared link.
  • Create a Template From HTML Creates a template from HTML containing field tags. Use HTML for a single document, or Documents when the template needs several, each with its own Page Size.
  • Create a Template From PDF Builds a template from PDF files. Turn off Remove Text Tags to keep {{text}} tags in the PDF, and use Folder to file the template.
  • Create Submissions From Emails Sends one template to every address in the comma-separated Emails list, giving each recipient a submission of their own. Turn off Send Email to skip the signature request emails.
  • Get a Submission Fetches one submission with its Status, Submitters, Template and Documents, plus a Combined Document URL.
  • Get a Submitter Reads one signer, including Opened At, Completed At, Declined At, Field Values and Documents.
  • Get a Template Returns one template with its Roles, Documents, Folder Name and Shared Link.
  • Get Submission Documents Retrieves the finalized documents of a submission. Turn on Merge Into One PDF to receive them combined as a single PDF.
  • List Submissions Lists submissions filtered on Template, Status or Search, which matches the name, email or phone of a submitter. Use Start After ID and Limit to page through a long list, or Archived Only for archived ones.
  • List Submitters Retrieves signers across your submissions. Filter by Submission, by Completed After and Completed Before, or by External ID, and page with Start After ID and Limit.
  • List Templates Gets templates, filtered by Search on part of the name, by Folder, or by External ID. Turn on Shared With Test Mode Only to see just the templates shared with test mode.
  • Make an API Call Makes an authorized free-form request to the DocuSeal REST API with your saved credential.
  • Merge Templates Joins two or more templates into one new template, keeping the order of Templates. Leave Name empty to get the first name with (Merged) appended.
  • Update a Submission Renames a submission through Name or shifts its Expires At deadline. Turn on Archived to archive it, or turn it off to unarchive.
  • Update a Submitter Edits a signer by Name, Email, Phone or External ID. Turn on Send Email or Send SMS to re-send the signature request, and Mark Completed to auto-sign through the API.
  • Update a Template Renames a template with Name, moves it with Folder, or renames its signer Roles in order. Set Archived on to archive it and off to unarchive.
  • Update Template Documents Adds or replaces the PDF or DOCX files behind a template using Documents. Turn on Merge Into Existing Documents to add alongside the current ones instead of replacing them.
  • Watch Forms Completed Fires through a webhook when one signer finishes their part of the form, even if others are still to sign. Output includes the Submitter with the Event Type and Timestamp.
  • Watch Forms Declined Runs the moment a signer declines to sign. The Submitter who declined arrives in the output.
  • Watch Forms Started Triggers once a signer begins filling in the form. Output includes the Submitter and the Timestamp.
  • Watch Forms Viewed Starts a run when a signer opens a form for the first time, passing on the Submitter and the Event Type.
  • Watch Submissions Archived Receives a webhook once a submission has been archived. Output includes the Submission along with the Timestamp.
  • Watch Submissions Completed Fires when every signer of a submission has signed, handing over the Submission together with the Event Type.
  • Watch Submissions Created Runs as soon as DocuSeal creates a submission, whether from the app or through the API, and passes on the Submission.
  • Watch Submissions Expired Triggers when the deadline of a submission passes while signatures are still pending. Output includes the Submission and the time of the event.
  • Watch Templates Archived Starts when DocuSeal archives a template, delivering the archived Template with a Timestamp.
  • Watch Templates Created Reacts to the creation of a template and hands the new Template to the next step with its Timestamp.
  • Watch Templates Updated Fires when the metadata or documents of a template are updated. Output includes the Template.

Explore alternative integrations

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

Automate ChMeetings and DocuSeal on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChMeetings and DocuSeal.

How do I connect ChMeetings and DocuSeal?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Archive a Submission" in DocuSeal. ChMeetings has 1 trigger (including Watch Events). DocuSeal has 24 actions (including Archive a Submission, Archive a Template, and Clone a Template). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore ChMeetings and DocuSeal, or get started