> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acelabusa.com/llms.txt
> Use this file to discover all available pages before exploring further.
# CRM Integration
> Every signal Acelab records for your brand can flow into your CRM, inbox, or spreadsheet through Zapier — with one trigger per signal type.
**Signals** are how Acelab records architects engaging with your brand and products — a product page opened, a product saved to a live project, a webinar registration.
Acelab sends **all of your signals to Zapier**. The same engagement you watch in the Accounts and Projects dashboards can land wherever your team already works: your CRM, a Slack channel, a spreadsheet, a task queue.
## One Zap per Signal Type
Every signal type is its own Zapier trigger. When you build a Zap you pick the specific signal you want to act on, rather than subscribing to everything and filtering it back down afterward.
That's deliberate, and it's what makes the integration useful: different kinds of engagement deserve different responses. High-intent project activity can open a task for the rep who owns the account, while brand page views quietly append a row to a spreadsheet nobody has to read.
### Firm Activity Triggers
Engagement tied to a firm.
| Trigger | Fires when |
| ----------------------------- | ------------------------------------------------------------------------------ |
| **Viewed Brand Page** | Someone at the firm opens your brand page. |
| **Viewed Product Page** | Someone at the firm opens one of your product pages. |
| **Saved to Library** | One of your products is saved to the firm's library. |
| **Saved to General Research** | One of your products is saved to the firm's general research. |
| **General Inquiry** | The firm starts a conversation with your team outside of any specific project. |
| **Registered for Event** | Someone at the firm registers for one of your webinars or events. |
| **File Downloaded** | Someone at the firm downloads a brand document or a product certification. |
### Project Activity Triggers
Engagement tied to a specific project.
| Trigger | Fires when |
| ------------------------- | ------------------------------------------------------------ |
| **Saved to Project** | One of your products is saved to a live project. |
| **Added to Spec** | One of your products is added to the project's spec. |
| **Mapped to Revit Model** | One of your products is synced to the project's Revit model. |
| **Info Request** | The firm starts a conversation about that specific project. |
Project activity is the higher-intent half. A firm browsing your brand page is looking; a firm putting your product into a live spec or Revit model is building with it. If you only wire up a few Zaps, start there.
## What Each Signal Delivers
Every signal Acelab sends to Zapier carries the same core fields, so a Zap you build for one trigger maps cleanly to the next:
* **Signal type** — which of the triggers above fired
* **The item** — the product, brand page, file, or event involved
* **The firm** — the architecture firm the engagement is attributed to
* **The project** — on project activity only, along with a flag telling you whether the project's name is still hidden
* **When** — the date and time it happened
Signals reach Zapier under the same visibility rules you see in-product. Acelab never sends you a signal from a firm that isn't on your Accounts dashboard, and never sends a project name that's still hidden from you in the product.
## What Stays Private
The data Acelab sends to Zapier is deliberately **firm-level**. It tells you that a firm is engaging, and what it engaged with — not which individual did it.
### Architect Names
At this time, Acelab **does not share the names of the architects behind a signal**. What arrives in your Zap is the firm and the action, not the person.
There is one exception: **events**. When someone registers for or attends one of your webinars or events, their name is shared with you, and the **Registered for Event** trigger carries its registrants by name. Registering is an explicit, opt-in introduction, so those names are yours to work.
This is Acelab's current privacy posture, not a permanent limit of the platform. If it changes, this page changes with it.
### Project Names
A project's name stays hidden until the firm signals real intent toward your products. Until then, signals about that project still reach your Zap — with the type, the location, the firm, and the product — but the name is withheld and flagged as hidden.
The name is released as soon as any of these happen on that project:
* The firm **saves one of your products** to it
* The firm **adds one of your products to the spec**
* The firm **maps one of your products to their Revit model**
* The firm **starts a conversation** about it
Because the flag travels with the signal, a Zap can branch on it — route named projects straight to a rep, and hold hidden ones in a nurture list until they open up.
## Choosing What to Automate
Sending every signal into a single Slack channel is the fastest way to get your team to mute it. A few patterns that hold up:
* **Route by intent, not by volume.** Wire **Added to Spec**, **Mapped to Revit Model**, and **Saved to Project** to something a person actually sees. Send the view-level signals somewhere they accumulate quietly.
* **Match the trigger to the owner.** Project activity usually belongs with the rep who owns that account; firm-wide views belong in reporting.
* **Let repeat interest build.** Page views are recorded once per person, per day, so a steady trickle of **Viewed Product Page** signals from one firm is a real pattern, not noise.
## Related
See the same signals in Acelab, before they reach Zapier.
Turn signal activity into a pipeline you can sort and work.
Reach an engaged firm without an email address.
Pick up the thread once a firm reaches out.