Intercom + Google Sheets: clean user records, fast
Customer data gets messy in boring ways. A signup comes in, someone creates (or half-creates) a user in Intercom, and the “source of truth” spreadsheet is already out of date.
This Intercom Sheets automation is a lifesaver for Support Leads trying to keep conversations tied to real users, and for Marketing Ops folks who need clean lists for campaigns. It also helps founders who are still doing cleanup themselves. You get consistent user records, logged every time, without the constant double-checking.
Below is how the workflow works, what it fixes, and how you can adapt it to your process so your team stops fighting the same data fires.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Intercom + Google Sheets: clean user records, fast
flowchart LR
subgraph sg0["Manual Run Start Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Run Start", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/intercom.svg' width='40' height='40' /></div><br/>Intercom User Creator"]
n0 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
classDef customIcon fill:none,stroke:none
class n1 customIcon
The Challenge: Duplicates and “Who Is This?” Intercom Users
Intercom is only as useful as the user data inside it. When users get created inconsistently (different emails, missing names, no signup context), your inbox turns into a guessing game. Someone asks “can you pull up their account?” and you’re clicking through near-identical profiles, trying to work out which one is real. Then marketing exports a list, support tags conversations, and suddenly you have three systems telling three different stories. It’s not dramatic. It’s just constant, and it burns time every day.
The friction compounds. It shows up in little moments that shouldn’t be hard.
- You end up creating users manually during live conversations, which is exactly when you’re most likely to miss a field.
- Duplicates creep in because one person signs up with a work email and later messages from a personal email.
- Google Sheets gets updated “later,” so you lose attribution details and the timeline of who signed up when.
- Teams start distrusting the data, so they build their own trackers, which makes the mess worse.
The Fix: Create the Intercom User, Log the Signup
This workflow creates an Intercom user on demand, using a consistent set of fields, and then records the signup in Google Sheets so you have a simple audit trail. It starts with a manual trigger (useful for testing, backfilling, or running it from an internal process), then pushes the user data into Intercom through the Intercom “create user” action. In practice, that means you stop relying on someone remembering the exact steps during a busy support shift. After the Intercom user is created, you can tie that event to a spreadsheet row, which becomes a lightweight ledger for marketing and support to share.
The workflow starts when you run it in n8n (or when you later swap the manual trigger for a real signup trigger). From there, Intercom gets the user record created in a predictable way. Finally, the same payload can be written to Google Sheets so you can filter, segment, and sanity-check without living inside your CRM.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Imagine you process about 30 new signups a day. Manually creating an Intercom user (find them, check duplicates, fill fields) can easily take 5 minutes, and logging it in Google Sheets is another minute or two. That’s roughly 3 hours of admin time every day when it gets busy. With this workflow, you trigger the run and let it create the Intercom user automatically; the only “time spent” is the initial input plus a quick spot check, which is closer to a few minutes total.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Intercom for creating and managing user profiles
- Google Sheets to log each created user event
- Intercom access token (get it from your Intercom developer settings)
Skill level: Beginner. You’ll connect accounts and map a few fields correctly.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Manual run kickoff. You start the workflow from n8n, which is perfect for testing and for backfilling users from a list.
User data gets packaged. The workflow prepares the fields Intercom needs (like email, name, and any custom attributes you choose to standardize).
Intercom creates the user. The Intercom node submits the record so you’re not relying on a human to remember which fields matter.
A Sheets log captures the event. Add a Google Sheets step to append a row (timestamp, email, Intercom user ID, source notes) so you can filter and reconcile later.
You can easily modify the input source to come from a form tool or product event instead of a manual run based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the manual trigger so you can test the Intercom user creation on demand.
- Add or confirm the Manual Run Start node as the trigger for the workflow.
- Ensure Manual Run Start is connected to Intercom User Creator to match the execution flow.
Step 2: Connect Intercom
Authenticate and configure the Intercom action that creates a user.
- Open Intercom User Creator and set Identifier Type to
email. - Leave ID Value empty if you plan to pass it dynamically from incoming data later.
- Credential Required: Connect your intercomApi credentials in Intercom User Creator.
Step 3: Configure Output Behavior
Verify the final action node is ready to create the user record in Intercom.
- Review Intercom User Creator and confirm no additional fields are required for your Intercom setup.
- Ensure the workflow connects Manual Run Start directly to Intercom User Creator with no interruptions.
Step 4: Test and Activate Your Workflow
Run a manual test to confirm Intercom user creation and then activate the workflow for use.
- Click Execute Workflow to trigger Manual Run Start.
- Check the output of Intercom User Creator for a successful response from Intercom.
- If the response is successful, toggle the workflow to Active for production use.
Watch Out For
- Intercom credentials can expire or need specific permissions. If things break, check your Intercom access token and app permissions in Intercom developer settings first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Common Questions
About 30 minutes if you already have Intercom access and a Sheets file ready.
Yes, but you’ll want someone detail-oriented to map fields carefully. No coding, just configuration and testing.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Intercom costs on your plan.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can replace the manual trigger with your real event source (a webhook from your app, a form submission, or a new row in Google Sheets) and keep the Intercom user creation step the same. Common customizations include adding “source” and “plan” as custom attributes, writing the returned Intercom user ID back into Sheets, and adding a duplicate-check before creating a new user (search by email, then update instead of create). If you also use other CRMs, you can branch: create in Intercom for support, then send the same payload elsewhere.
Usually it’s an expired or revoked access token. Regenerate your Intercom token, then update the credentials inside n8n and re-run a single test execution. Also check that your Intercom workspace allows the user create action (some roles and apps are restricted), and watch for rate limits if you’re backfilling a big list in one go.
On n8n Cloud Starter, you can run thousands of executions a month, which is enough for many small teams. If you self-host, there’s no fixed execution limit; it mostly depends on your server and how fast Intercom and Google Sheets respond. In real use, most teams can process signups as they come in without any batching at all.
Sometimes. If all you need is “create user, add row,” Zapier or Make will work fine and feel simpler. n8n starts to win when you add real logic: lookup-before-create, branching based on domain or plan, or writing back Intercom IDs and error details for auditing. Self-hosting is also a big deal if you run lots of executions and don’t want per-task pricing. If you want, Talk to an automation expert and we’ll tell you bluntly which route is smarter for your setup.
Clean Intercom users and a trustworthy signup log changes how fast your team can move. Set it up once, and let the workflow handle the repetitive cleanup.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
