Update a ChMeetings person from a 0CodeKit webhook
Keep directory records current while the source process still has the latest information.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
ChMeetings: Update Person
Tool to update an existing person's information in ChMeetings. Use when modifying person details; call after retrieving person ID via CHMEETINGS_PEOPLE_LIST or CHMEETINGS_PEOPLE_GET. Supported update fields (use snake_case): - Personal: first_name, last_name, middle_name, nick_name, native_name, email, mobile, telephone, birth_date - Demographics: gender (Male/Female/Unknown), social_status (Single/Married/etc.) - Professional: job_title, work_place, qualification, education_level, school - Religious: church, baptism_date, baptism_location, is_deacon, rank, bishop_donor - Communication: do_not_text, do_not_email (boolean) - Address: address object with country, state, city, etc.
Why this helps
Directory edits are easy to postpone when updated details arrive through another automation.
- Keeps person records current
- Reduces repetitive data entry
- Reports the updated record context
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and ChMeetings in Notis.
- 2Create an automation for person record updates.
- 3Tell Notis to update the identified ChMeetings person with the approved details and report when the person ID is unavailable.
- 4Choose the webhook trigger and report channel, then test with one real update.
Questions about this workflow
Does the request need a person ID?
Yes, provide the ChMeetings person identifier or enough approved context for your process to supply it.
Can it update unsupported fields?
Notis can only use fields supported by the ChMeetings action and should report unsupported requests.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 0CodeKit to Chmeetings. A trigger fires from one place; an action lands in another.
0CodeKit triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
ChMeetings: Create Organization
Tool to create a new organization.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
Delete Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
0CodeKit and Chmeetings, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Chmeetings.