Aboard Sign and ChMeetings Integration

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

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

Detailed info you need to know about Aboard Sign and ChMeetings integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Aboard Sign

    • Productivity
    • 3 searches
    • 4 actions

    Get a document signed by email, check where a signing stands, and verify a signed copy. Aboard Sign allows only a few signings per day from one address, and WEXTL calls from shared addresses, so the daily limit may be reached early.[5]

  • ChMeetings

    • Productivity
    • 1 trigger
    • 60 searches
    • 50 actions

    Church management software for people, giving, events, groups and communication.[6]

How to connect Aboard Sign to ChMeetings

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

How does the integration between Aboard Sign and ChMeetings work in WEXTL?

WEXTL exposes actions and triggers for Aboard Sign and ChMeetings 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 triggersAboard Sign 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.

Aboard Sign modules

  • Get a Signing Status Looks up an open signing by its Signing ID and reports who has signed and who is still awaited. A signing that is over returns the state gone instead of an error.
  • Get Log Entries Finds a document on the public log by its Fingerprint. A listed document means everyone signed, and an empty entries list means signatures are still missing.
  • Get the Public Key Fetches the key that countersigns every record, as a Key ID and a Public Key. It works without a site password, so a record can be checked outside the app.
  • Make an API Call Calls the Aboard Sign REST API directly with a free-form request, adding the site password when one is saved.
  • Start a Signing Mails every named person a link of their own to sign a document typed in as text. Needs a Sender Email and a Document, and the sender signs too.
  • Start a Signing from a File Sends an uploaded PDF, DOCX, RTF, Markdown or text file out for signature by email. Add up to four Signers besides the sender, and set a File Name when the mapped file has none.
  • Verify a Signed Copy Uploads a Signed PDF and checks every page, every signature and the seal. The answer holds a Verdict, a list of Problems and the Signers, and the vendor keeps nothing that is sent.

Explore alternative integrations

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

Automate Aboard Sign and ChMeetings on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Aboard Sign and ChMeetings.

How do I connect Aboard Sign and ChMeetings?

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

Example: when the "Watch Events" trigger in ChMeetings fires, WEXTL can "Get a Signing Status" in Aboard Sign. Aboard Sign has 7 actions (including Get a Signing Status, Get Log Entries, and Get the Public Key). ChMeetings has 110 actions (including Add a Person to a Group, Add a Person to an Organization, and Add Family Members). Add filters and transforms between steps when you need them.[1]

Can Aboard Sign trigger actions in ChMeetings, and ChMeetings in Aboard Sign?

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 Aboard Sign and ChMeetings?

No. Aboard Sign-to-ChMeetings automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Aboard Sign integrate with ChMeetings in real time?

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

You can build your Aboard Sign + ChMeetings automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Aboard Sign and ChMeetings integration.

  1. Aboard Sign and ChMeetings integration source code, module specs and credentials implementation.
  2. Our Aboard Sign and ChMeetings integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Aboard Sign and ChMeetings, 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. Aboard Sign integration information
  6. ChMeetings integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Aboard Sign and ChMeetings integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Aboard Sign and ChMeetings, or get started