Zapier
Wire StackScan into the tools you already use, no code.
On this page
What the Zapier integration does
Zapier connects StackScan to around 8,000 other apps without any code. The usual shape is that something happens in a tool you already use, StackScan answers a question about a domain, and the answer goes back where it is useful.
New company in HubSpot → StackScan: Find Technologies by Domain → Update the company
Currently invite-only
The StackScan Zapier integration is in private release. It is fully working, but it is not yet listed in Zapier's public App Directory, so you cannot find it by searching inside the Zap editor.
To use it, ask us for an invite and we will send you a link that adds StackScan to your Zapier account. Everything below works the moment you accept.
What you can build with
No trigger. StackScan answers questions about a domain rather than emitting a stream of records, so there is nothing honest to wake a Zap up. Your Zap starts somewhere else and calls StackScan in the middle.
Three searches, for use in the middle of a Zap:
| Search | Give it | Get back |
|---|---|---|
| Find Technologies by Domain | a domain | every technology on that site |
| Find Company by Domain | a domain | the company behind it |
| Find Technology Usage | a technology name | how many sites run it, and where |
Two actions:
| Action | What it does |
|---|---|
| Bulk Look Up Technologies | up to 100 domains in one step |
| Start Technology List | begins a whole-technology export |
What it costs
Searches and the bulk action spend bulk-lookup credits, charged per domain that resolves. Domains we have no data for are not charged.
Starting a technology list spends 1 standard credit, flat, no matter how large the list is. It costs nothing at all if you already requested that technology in the current billing period. Standard and bulk-lookup credits are separate balances.
Zapier also counts every step as a task against your own Zapier plan, which is billed by Zapier, not by us.
Two limits worth designing around
A Zap cannot end with a search. Zapier requires a search to be followed by something that uses the result, so a Zap built around Find Technologies needs a third step: update a record, send a message, add a row.
A search that finds nothing stops the Zap. That is Zapier's behaviour, not an error on our side. If you are running domains from a list where some will miss, expect halted runs and treat them as normal.
Connecting your StackScan account to Zapier
Connecting takes about a minute and needs two values from your dashboard.
1. Get your API token
In StackScan, open My Account → API Tokens and create a token. It is shown once, so copy it before you leave the page. If you lose it, revoke it and make another; there is no way to read an existing token back.
2. Accept the invite
The integration is in private release and is not in Zapier's public directory yet, so you need an invite link from us. Ask for one here. Opening it while signed in to Zapier adds StackScan to your account.
3. Add the connection
In Zapier, add any StackScan step to a Zap and choose Sign in. You will be asked for:
- API Token: the value you copied in step 1.
- Workspace: a dropdown. It fills itself in from your token, so you should see your workspaces by name rather than having to paste an ID.
If the workspace dropdown is empty, the token is the problem, not the workspace. See below.
Which workspace to pick
If you belong to more than one workspace, the choice matters: each workspace has its own credits and its own data. Picking the wrong one means spending the wrong balance. The connection is labelled with the workspace name and your email so you can tell two connections apart at a glance.
To use two workspaces in one Zapier account, add StackScan twice as two separate connections.
When something is wrong
"Your StackScan API token is not valid." The token was mistyped, or it has been revoked. Create a fresh one and reconnect. Zapier also emails you when a connection stops authenticating, so you are not left guessing why a Zap went quiet.
The workspace dropdown is empty. The token is valid but the account is not a member of any workspace yet, or the token was pasted with surrounding whitespace.
A step fails with "not enough credits". Check which balance it needs. Searches and bulk lookups spend bulk-lookup credits; technology lists spend standard credits. A full balance of one will not pay for the other.
Revoking access
Deleting the token in My Account → API Tokens immediately stops every Zap using it. Removing the connection inside Zapier does the same from the other end. Do the first if you think a token has leaked: it takes effect at once and does not depend on anyone being signed in to Zapier.
Example Zaps
Four patterns that cover most of what people build. Each says what it costs, because every StackScan step spends credits.
Enrich a new CRM company
New Company in HubSpot
→ StackScan: Find Company by Domain
→ Update Company in HubSpot
The classic one. A company arrives in your CRM with nothing but a website, and leaves with an industry, a location and a size.
Cost: 1 bulk-lookup credit per company that resolves. Companies we hold no record for are free.
Swap the second step for Find Technologies by Domain if you want the stack rather than the firmographics. Useful for routing a lead to whoever knows that platform.
Alert a channel when a prospect runs your competitor
New Row in Google Sheets
→ StackScan: Find Technologies by Domain
→ Filter: Technologies contains "<competitor>"
→ Send Channel Message in Slack
The Filter step is doing the work: the search returns the whole stack, and the filter decides whether it is interesting. Put the filter after the lookup, not before, because you cannot filter on data you have not fetched yet.
Cost: 1 bulk-lookup credit per domain. The filter and the Slack message are free on our side.
Enrich a whole list at once
New or updated rows in Google Sheets
→ StackScan: Bulk Look Up Technologies (up to 100 domains)
→ Create Spreadsheet Rows in Google Sheets
One step for up to 100 domains, which is much cheaper in Zapier tasks than looping. The action returns a Summary field, a plain-text roll-up, so you can drop the result into an email or a message without a Formatter step.
Trigger on the list changing rather than on a timer. Our detections change when we recrawl the web, so re-scanning the same domains every week spends credits to be told what you already knew.
Cost: 1 bulk-lookup credit per domain that resolves.
Kick off a technology list on a schedule
Schedule by Zapier (monthly)
→ StackScan: Start Technology List
→ Send Email with the Status URL
Technology lists take minutes to build, so this action starts one and returns immediately with a Status URL rather than waiting. Email that link to yourself and open it when you are ready; the file is there once status reads ready.
A Zap cannot carry the file itself. Lists run to millions of rows and can be over a gigabyte, so what a Zap can pass along is the link and the counts, never the data.
Cost: 1 standard credit, whatever the size of the list. A repeat of the same technology inside one billing period is free, so a monthly refresh still costs one credit a month.
Before you rely on any of these
Run each Zap once by hand and look at the result rather than trusting that it worked. The two things that surprise people are a search finding nothing (which stops the Zap, and that is Zapier's behaviour rather than a fault) and a truncated list (check Truncated By Plan Limit before treating a file as the full population).