Plan for who’s coming.
Know who came.

Salesforce, at whatever pace your admins can manage

• Start without a ticket. Anyone who can build a Salesforce report can subscribe it to a ChapterIQ email address with the file attached. Your roster then updates itself on a schedule, and no administrator has to be involved.
• Move to a live connection in fifteen minutes of admin time. When your admins are ready, we give them an installable permission set, an illustrated runbook, and a one-page security summary they can paste into their internal ticket. There is nothing to design, no custom fields, and no change to your org.
• The live connection uses a dedicated integration user. Its permission set grants read access to Accounts, Contacts, and only the fields you choose to map.
• Record visibility is limited to your division inside Salesforce itself. ChapterIQ applies its own filter as a second layer, never as the only one.
• The initial load runs through the Bulk API, and incremental syncs run on a schedule. Paid Change Data Capture is not required.
• Dietary and accommodation details never leave ChapterIQ. If you turn on write-back, it is limited to Campaign Member status.
• One screen in ChapterIQ shows exactly what this vendor can see, and you can export it for a security review.

HubSpot, connected with one private app

Your HubSpot administrator creates a private app in a few minutes and gives it read access to companies and contacts. That token is the whole connection. ChapterIQ then asks two questions: which company property says that a company is a member, and which property or association says which chapter it belongs to. Most networks already have both.

Companies and their contacts sync on a schedule, and a contact who changes employer in HubSpot moves to the new member company in ChapterIQ on the next sync. If you want participation in HubSpot, ChapterIQ can write a small set of properties to each company, such as last attendance and engagement tier, and post a timeline event when a company attends a meeting. Those show up in lists, workflows, and reports like any other property.

This works on any HubSpot tier, including the free CRM. Nothing here requires Operations Hub or a custom object.

Dynamics 365, in the tenant your staff already sign in to

Because your staff sign in to ChapterIQ with their Microsoft 365 accounts, the connection to Dynamics lives in the same Microsoft Entra tenant. Your administrator registers ChapterIQ as an application once, creates an application user in Dataverse, and assigns it a security role that reads Accounts and Contacts. We supply the role definition and a step-by-step guide, and the whole thing takes about twenty minutes.

ChapterIQ reads through the Dataverse Web API using change tracking, so each sync moves only the records that changed since the last one. Membership and chapter come from whichever fields you already use for them. Write-back, if you turn it on, goes to a small set of custom fields on the Account or to a Campaign Response, and the guide includes the solution file that adds them.

Dynamics 365 Sales and Customer Engagement are both supported, as is a plain Dataverse environment behind a Power Apps model-driven app.

monday.com, board by board

monday.com is not a fixed CRM schema. It is whatever boards your team has built, so ChapterIQ starts by asking which board holds your member organizations and which one holds their people. If you use monday CRM, those are the Accounts and Contacts boards, and ChapterIQ finds them on its own. If you built your own boards, you point at them and at the columns that matter, including the one that links a person to their company.

Your monday.com administrator creates an API token for a dedicated integration user, or installs the ChapterIQ app from the monday.com marketplace once it is listed there. ChapterIQ reads the boards on a schedule and also subscribes to board webhooks, so a new member company or a changed email address reaches ChapterIQ within a minute rather than at the next sync. Membership status and chapter come from the columns you map. If there is no chapter column, ChapterIQ can assign chapters from an address column.

Write-back, if you turn it on, fills a few columns on each organization item, such as last attendance and engagement tier, and posts an update on the item when the company attends a meeting. Participation then shows up in the same boards, automations, and dashboards your team already uses.

A spreadsheet is a perfectly good membership database

Plenty of networks keep their roster in Excel, and ChapterIQ treats that as a first-class source. Download our template, which has one sheet for member organizations and one for people, fill it in or paste from what you already have, and upload it. ChapterIQ shows you what it understood before it saves anything.

Every upload updates the roster in place rather than adding to it. Organizations are matched by an identifier you choose, people by email address, so uploading last month’s file with twenty changes produces twenty changes and no duplicates. Rows that disappear from the file are marked inactive, never deleted, and you can see exactly which rows each upload touched.

If someone already produces this file on a schedule, they can email it to your ChapterIQ import address instead of uploading it. That is also how the Salesforce report subscription works, and it means the roster stays current without anyone remembering to do anything.

Staff sign in with the account they already have

ChapterIQ has no passwords of its own. Staff click Sign in with Microsoft and use their Microsoft 365 work account, which means the multifactor and conditional access rules your IT department already set apply to ChapterIQ automatically. When someone leaves the organization and their account is disabled, their ChapterIQ access ends with it.

The first person from your organization to sign in creates the workspace, and colleagues who sign in from the same verified email domain join it rather than creating their own. An administrator can also invite people directly and assign them to chapters. Your Entra administrator sees a single consent screen the first time, listing exactly what ChapterIQ asks for, which is the ability to read the signed-in user’s name and email address and nothing else.

Organizations that want to require their own identity provider, restrict sign-in to particular groups, or provision users automatically can do that with enterprise single sign-on on the Scale and Enterprise plans.

The same thing for Google Workspace

Organizations that run on Google Workspace get the same arrangement. Staff click Sign in with Google and use their work account, ChapterIQ receives their name and email address, and nothing else about the account is visible to us. Two-step verification and any other policy the Workspace administrator has set carry over.

A network with a mix of both is fine. Headquarters can be on Microsoft while a chapter’s volunteer leader signs in with a Google account, and either kind of account can be assigned to any role. What matters to ChapterIQ is the verified email domain and the role you gave the person, not which company issued the account.

Personal Gmail and Outlook.com accounts can be invited when a chapter is run by a volunteer who has no work account, and an administrator can turn that off for the whole organization.

Everything on the screen is available to your own code

The REST API exposes the same data the application uses: organizations, people, chapters, events, invitations, responses, check-ins, and the participation figures computed from them. It is documented with an OpenAPI description, so you can generate a client in whatever language your team uses, and every endpoint page includes a working example.

API keys belong to your organization and can be limited to particular chapters and to read-only use. A key can list who attended last quarter’s meetings, but it can also create an event from a template, add invitees, or record a check-in from a badge scanner you already own. Every call is logged with the key that made it.

Common uses so far are a nightly pull into a data warehouse, a Power BI report on chapter participation, and a membership team’s own renewal dashboard that shows attendance next to dues.

Ask your AI assistant about your own meetings

ChapterIQ hosts a server that speaks the Model Context Protocol, the open standard that lets AI assistants such as Claude, ChatGPT, and Microsoft Copilot use outside tools. Connect it once and a chapter manager can ask, in plain words, which Central Wyoming companies have not attended since March, or how this year’s no-show rate compares with last year’s, and get an answer drawn from the live data.

The server uses the same keys and the same permissions as the REST API, so an assistant can see only what the person who connected it can see. It is read-only unless you deliberately issue a key that allows writes, and every question it answers is logged in the same place as every API call.

This is the piece we expect to matter most to small teams. An analyst is a luxury most networks do not have, and this gives every chapter manager something close to one.

Tell your other systems the moment something happens

A webhook is a message ChapterIQ sends to a web address you give it whenever something you care about happens. When a meeting closes, when someone responds to an invitation, when a member is checked in at the door, or when a company’s engagement tier changes, ChapterIQ posts the details to your endpoint within seconds.

That is how a meeting’s closing can start a Power Automate flow that files the sponsor report in SharePoint, or how a Zapier zap can post the headcount to a Slack channel, or how your own code can update a renewal system the moment a lapsed company shows up again. Each message is signed so your endpoint can verify it came from ChapterIQ, and if your endpoint is down, ChapterIQ retries for a day and keeps a log you can replay from.

A calendar entry that behaves like one

Every invitation ChapterIQ sends carries a standard calendar attachment, so the meeting lands on the invitee’s calendar as a tentative hold the moment the invitation arrives. When they say yes, the entry becomes firm. When the time or venue changes, the entry updates. When they decline, or the meeting is canceled, it disappears. This works in Outlook, Google Calendar, and Apple Calendar without anyone installing anything.

What is different from sending an Outlook meeting request is that the accepts and declines do not come back to the chapter manager’s mailbox. The RSVP page collects the answer, along with the questions an Outlook invitation cannot ask, and the calendar entry simply reflects it.

Chapter managers can also subscribe to a feed of their own chapters’ meetings, so the events show on their calendar with the current headcount in the description and a link straight to the event.