Keep member contact preferences up to date
A communication preference change deserves follow-through. Notis can carry the request from Linear into the right ChMeetings person record.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
A preference noted during support or coordination can be missed when the directory is maintained separately.
- Reduce the chance of contacting someone against their stated preference.
- Keep member records aligned with coordination work.
- Avoid a separate reminder to update the directory.
Setup
Build it in a few focused steps.
- 1Connect Linear and ChMeetings to Notis once in the portal.
- 2Create an automation or ask Notis to update a ChMeetings person when a Linear issue records a contact preference change.
- 3Give one plain-language instruction describing how to identify the person and apply the requested preference.
- 4Select the Linear Issue Updated trigger and a run-report channel.
- 5Test with an authorized preference update and verify the correct person record.
Questions about this workflow
Can it update do-not-text or do-not-email?
The ChMeetings person update action supports communication preference fields. Describe the requested change in the instruction.
How should the right person be identified?
Include reliable identifying context in the Linear issue and explain in the instruction how Notis should find the matching ChMeetings person.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Chmeetings. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
ChMeetings: Create Organization
Tool to create a new organization.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Delete Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.