Connecting Zapier
1
Get access to the Acelab app
The Acelab Zapier app is invite-only for now. Ask your Acelab contact for the invite link, open it while signed in to Zapier, and accept. Acelab then shows up when you search for an app to start a Zap.
2
Get an API key
An Org Admin of your organization creates keys in Acelab: go to My Account → Integrations, click Create API Key, give it a label (for example, “Zapier — HubSpot sync”), and copy the key that appears. Each key covers all of your organization’s brands (see One Key for All Your Brands) and starts with
ak_. Admins can show and copy any key again later from the same page, so there’s no need to store it elsewhere.Not an Org Admin? You won’t see Integrations in your menu; ask one of your organization’s admins. API keys are a paid add-on: if your plan doesn’t include them, Create API Key shows a Contact Sales button instead.Have a key Acelab gave you before self-serve keys? It no longer works. Create a new key and reconnect your Zaps with it.3
Pick a trigger
In Zapier, create a Zap, choose Acelab as the trigger app, and pick the signal type you want from the lists below.
4
Connect your account
When Zapier asks you to sign in to Acelab, paste your API key. Zapier checks it right away and labels the connection with your organization’s name.
5
Test and turn it on
Test trigger loads the most recent signals of that type across your brands. If you don’t have any yet, it loads a realistic example instead, so you can still map fields. Add your action, then turn the Zap on.
Using the older New Lead or Lead Updated triggers? They’ve been replaced by the signal triggers below. Rebuild those Zaps on the signal you want.
Managing Your API Keys
Org Admins manage every key on My Account → Integrations:- Rename a key by editing its label.
- Keys expire one year after they’re created. An expired key stops working, so its Zaps stop receiving signals. Click Extend on the expired key to give it another year: the same key works again and your Zaps pick up new signals without reconnecting. Signals from while it was expired aren’t sent later.
- Delete a key you no longer use. This is permanent: it stops working immediately, and any Zaps using it stop receiving signals. To keep those Zaps going, create a new key, reconnect the Acelab account in Zapier with it, and turn the Zaps off and on again.
- If your plan stops including API access, all of your organization’s keys expire.
One Key for All Your Brands
An API key belongs to your organization, not to a single brand:- Manufacturers: the key covers every brand your organization owns.
- Distributors and rep firms: the key covers every brand you actively carry. You receive the same signals the manufacturer receives for each of those brands, under that brand’s rules. That’s more than your own Accounts and Projects dashboards show, so for you Zapier is the wider view. When a brand stops being one you carry, its signals stop, including any that were waiting to be delivered.
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. There is no catch-all “any signal” trigger. To act on several signal types, build a Zap for each. 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.Project Activity Triggers
Engagement tied to a 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 ID — a stable ID for the signal. Zapier uses it to avoid running a Zap twice for the same signal.
- Signal type — which of the triggers above fired
- Brand — which of your organization’s brands the signal was recorded on, by ID and name
- Label — the product, brand, file, or event involved. On Appeared in Search it’s the search the architect typed, exactly as they typed it. It’s empty on General Inquiry and Info Request.
- The firm — the architecture firm the engagement is attributed to
- The project — on project activity only: its ID and details such as phase, budget and location, plus its name, description and architect once the project is revealed to you
- When — the date and time it happened, in UTC
Signals reach Zapier under the same visibility rules you see in-product. Acelab only sends signals from firms that qualify for your Accounts dashboard (see When a Zap Fires for firms you delete), and never sends the name or description of a project that’s still hidden from you in the product.Distributors and rep firms receive each carried brand’s signals under that brand’s rules, the same ones its manufacturer sees. That’s wider than your own Accounts dashboard. When the manufacturer deletes a firm, that firm’s Firm Activity triggers stop firing for you too; deleting a firm from your own dashboard doesn’t change what Zapier sends.
When a Zap Fires
Signals record new engagement, not every click. Repeat activity is grouped, so a Zap fires less often than raw activity would suggest:
Days are counted in UTC, not your local time zone.
A few more things to expect:
- Only new activity. A Zap fires for signals recorded after you turn it on. It doesn’t replay your history. Your full signal history stays in the Accounts and Projects dashboards (for distributors and rep firms, the manufacturer view Zapier delivers is wider than those dashboards).
- The brand’s own team’s browsing doesn’t count. When people at the brand’s company view your pages, download your files, save your products, or register for your events, Acelab doesn’t record a signal, so no Zap fires. Conversations are the exception: a conversation counts for the firm it’s with, whoever starts it, so General Inquiry and Info Request fire even when your team starts the conversation.
- Only qualifying firms. Activity from firms that don’t qualify for the brand’s Accounts dashboard never leaves Acelab.
- Deleting a firm stops its firm activity. When the brand deletes a firm from its Accounts dashboard, its Firm Activity triggers stop firing. Its Project Activity triggers keep firing, because deleting a firm doesn’t remove its projects from your Projects dashboard.
- A delivery can occasionally be missed. Acelab sends each signal to Zapier once. If Zapier can’t be reached, Acelab keeps retrying for several hours. If a delivery is still lost, the signal stays visible in Acelab, but that Zap won’t run for it later. Treat your Zaps as a fast notification layer, and use Acelab’s dashboards as the record of what you can act on in the product.
What Stays Private
Signals are mostly firm-level. They tell you that a firm is engaging, and what it engaged with, but not which individual did it.People’s Names
Signals from browsing, downloads, searches and saves name the firm, not the person. Acelab shares a person’s name only where you already see it in Acelab:- Event registrants. Registering for one of your webinars or events is an explicit, opt-in introduction, so those names are yours to work. Registered for Event carries every registrant by name.
- Who started a conversation. Info Request and General Inquiry carry the name of whoever started the conversation. That can be someone at the firm, your own rep or Acelab staff.
- A visible project’s architect. Project activity carries the architect named on the project once the project is visible to you.
Project Names
A project’s name stays hidden until the firm signals real intent toward your products. 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
- A conversation with your team starts about it
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 Product Saved to Project to something a person actually sees. Send the view-level signals and Appeared in Search 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
Navigating the Dashboards
See the same signals in Acelab, before they reach Zapier.
Organizing Your Accounts and Projects
Turn signal activity into a pipeline you can sort and work.
Using Proxy Email
Reach an engaged firm without an email address.
Conversations Overview
Pick up the thread once a firm reaches out.

