- Home
- Resources
- Integrations
- Common Room
Common Room Zapier integrationAutomate Common Room with Zapier.
The Common Room Zapier integration gives you 2 triggers and 9 actions to push contacts, organizations, activities, tags and notes into your room from other tools. The two triggers are polling ones, and the app works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Common Room Zapier integration is really for
Common Room gathers the people around your product, your community members, users and prospects, in one place it calls a room. On Zapier, the strong side of the integration is writing: nine actions feed contacts, organizations, activities and notes into that room from tools it does not reach on its own.
Contacts from a tool Common Room does not watch. A developer relations lead runs a meetup sign-up form somewhere else. Add Contact From Third Party Source brings each attendee into the room, keyed on that tool's own user ID.
Activity that counts toward the contact's story. Add Activity From Third Party Source logs what someone did elsewhere, a talk given or a course finished, on their Common Room contact.
Segments that stay current. Add Common Room Contact to Segment and Add Tags to Common Room Contact sort people by email or another identifier the moment the other tool knows something new.
What Zapier does not do well here: the two triggers only watch the list of custom fields and the statuses of a segment. None of the eleven operations starts a Zap from something a contact does. If you need Common Room as a starting point, read the n8n vs Zapier comparison, or ask our Zapier agency to scope it.
Zapier words you will meet on this page
Eight terms in plain English. Each one comes back further down without a second explanation.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it to happen.
- Action
- What the Zap does once started: the step that writes, sends or changes something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- Zapier checks a polling trigger on a timer, keeping only what it has not seen. An instant trigger is reported by the app itself.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
- Connection
- Your Common Room account linked to Zapier once, then reused by every Common Room step in every Zap.
What a Common Room Zap costs you in tasks
Zapier bills completed actions, not the checking. Common Room is not a premium app, so it runs on the free plan (operations read on 1 October 2026, integration version CommonRoomCLIAPI@3.1.0).
- Trigger and checksFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, Common Room works on the free plan
The trigger never costs a task, and neither does Zapier checking for new items, however often it looks. Each action that succeeds counts once, so a three-action Zap uses three times what a one-action Zap uses. A failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. A filter or a second action makes it a multi-step Zap, which needs a paid plan. Because both triggers are polling ones, your plan also sets how fast a Zap reacts, as the grid below shows.
Connect Common Room to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. Type Common Room in the search box of the dialog, then select it from the list of results.
- 02
Sign in to Common Room
Click Add connection. A tab opens on Common Room: sign in with the account your Zaps should act as. It needs write access to the contacts, organizations and segments you plan to touch.
- 03
Grant access
Allow Zapier to use the account. Every Common Room step in every Zap reuses this connection from then on, so you set it up once and pick it while you build.
Your first Zap: a new segment status, written down and announced
GoalWhen a new status appears on the segment you watch, that same segment gets a note naming it, and your team chat hears about it.
- 01
Build: pick the trigger
Start a new Zap, choose Common Room and the Segment Status List event, then your connection, and set it on the segment you want to follow. There is no lightning bolt here: this trigger is a polling one.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items the trigger can see, so you write the next steps on a real status rather than on a blank sample.
- 03
Add the note
Click the plus icon and choose Add Note to Segment. Point it at the same segment and write the note, mapping the status from the trigger. The note is the one required field.
- 04
Tell the team
Add a step from your team chat that posts a short message with the same status, so nobody has to open Common Room to notice the change.
- 05
Test, then publish
Test each step and check the segment in Common Room. Click Publish. With two actions, this is a multi-step Zap, so it needs a paid plan.
Common Room triggers: two polling ones
2 events start a Zap when something happens in Common Room. Zapier checks for them at the interval your plan allows.
Custom Fields List
Polling triggerIn Zapier“List of Custom Fields”
Watches the list of custom fields defined in your room. Since Zapier keeps only what it has not seen before, the Zap starts when a field appears in that list after you switch it on.
Segment Status List
Polling triggerIn Zapier“List of Status for a Segment”
Reads the list of statuses available for a segment. A status Zapier has not seen yet is enough to start the Zap, so it follows how your segment workflows evolve over time.
Common Room actions: what your Zap can write
Common Room gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Activity From Third Party Source
ActionIn Zapier“Adds an activity to a contact in your room.”
Logs something a person did in another tool on their Common Room contact.
Add Contact From Third Party Source
ActionIn Zapier“Adds a contact to your room.”
Brings a person into your room from another tool, identified by that tool's own user ID.
Add Note to Common Room Contact
ActionIn Zapier“Adds a note to a contact in your room.”
Attaches a note to a contact found by an identifier.
Add Note to Segment
ActionIn Zapier“Adds a note to a segment in your room.”
Adds a note to a segment rather than to a person.
Add Organization From Third Party Source
ActionIn Zapier“Adds an organization to your room.”
Creates an organization in your room, identified by its domain.
Add Tags to Common Room Contact
ActionIn Zapier“Add new or existing tags to a contact in your room.”
Adds new or existing tags to a contact found by an identifier such as an email.
Add Common Room Contact to Segment
ActionIn Zapier“Adds one or more contacts in your room to a segment.”
Places one or more existing contacts in a segment of your room.
Get a Common Room Contact
ActionIn Zapier“Gets information on a contact in your room.”
Fetches the information of a contact from an identifier and hands it to the steps that follow.
Add or Update a Contact Custom Field
ActionIn Zapier“Add or update a contact custom field.”
Writes a value into a custom field of a contact, adding it or replacing what was there.
When a Common Room Zap breaks
Zapier attaches no help article to Common Room. The cases below come from how Zaps behave in general and from what the Common Room fields require.
Most trouble on this integration comes from identifiers: the ID you send decides whether Common Room creates something or overwrites it. If a run fails and you cannot see why, the Zapier troubleshooting guide is the next stop.
A reused user ID overwrites a contact
If two people reach Common Room with the same user ID, the second updates the first person's contact instead of creating a new one.A reused activity ID replaces an activity
Each activity needs its own unique ID. Send the same ID twice and Common Room updates the earlier activity rather than adding another.A missing Destination ID
Four actions need the Destination ID from Settings, Signals, API in Common Room. Without it the step cannot run.A wait before the Zap reacts
Both triggers are polling ones. On the free plan Zapier checks every 15 minutes, so a new status can sit there until the next check.Nothing from before is picked up
A Zap only reacts to what appears after you switch it on. Fields and statuses that already existed are not picked up.A bulk change that gets held back
If a large batch of new items appears at once, Zapier's flood protection can hold the runs back instead of firing them all.
Need help automating Common Room with Zapier?
A person reads every message.



