Zapier Integration

Zapier connects Context.dev to 9,000+ apps. You bring the trigger (Typeform submission, new HubSpot contact, new Gmail email) and Context.dev provides the enrichment action.

Install the Context.dev Zapier app

Authorize Context.dev inside Zapier and connect your API key.

What you get

Version 3 of the Context.dev Zapier app ships 16 actions. Zapier splits them into search actions, which look something up and return data, and write actions, which kick off work. Every action calls the same endpoint you would hit directly via the API, at the same credit cost.

Search actions

Action	Input	Output	Endpoint
Retrieve Brand Data by Domain	Domain	Full brand record (logos, colors, description, socials, industry, address)	`POST /brand/retrieve` with `type: "by_domain"`
Retrieve Brand Data by Company Name	Company name, 3 to 30 characters	Full brand record	`POST /brand/retrieve` with `type: "by_name"`
Retrieve Brand Data by Email Address	Work email address	Full brand record for the email’s domain	`POST /brand/retrieve` with `type: "by_email"`
Retrieve Brand Data by Stock Ticker	Ticker plus optional exchange (defaults to NASDAQ)	Full brand record	`POST /brand/retrieve` with `type: "by_ticker"`
Retrieve Brand Data by ISIN	12-character ISIN, e.g. `US0378331005`	Full brand record	Zapier-only lookup; `POST /brand/retrieve` has no ISIN type yet
Retrieve Simplified Brand Data by Domain	Domain	Domain, title, colors, logos, and backdrops only	Trimmed brand payload, faster and smaller than the full record
Identify Brand From Transaction Data	Transaction descriptor plus optional country, city, MCC, and phone	Brand record for the merchant	`POST /brand/retrieve` with `type: "by_transaction"`
Retrieve NAICS Code for Any Brand	Domain or company name plus optional min and max result counts	2022 NAICS codes with confidence	`GET /web/naics`
Take Screenshot of Website	Domain plus optional full-page flag and page type (`pricing`, `login`, …)	Hosted screenshot URL with width and height	`GET /web/screenshot`
Extract Design System and Styleguide From Website	Domain	Colors, typography, spacing, shadows, and UI components	`GET /web/styleguide`
Extract Fonts From Website	Domain	Font families with usage stats and fallbacks	`GET /web/fonts`

Write actions

Action	Input	Output	Endpoint
Extract Products From a Brand’s Website	Domain plus optional maximum number of products (1 to 12)	Product list with names, prices, images, features	`POST /brand/ai/products` (beta)
Query Website Data Using AI	Domain, one or more data points (name, type, description, example), optional page filters	Extracted value per data point	Legacy extraction action; new API builds should use `POST /web/extract`
Prefetch Brand Data for a Domain	Domain	Queued confirmation	`POST /utility/prefetch` (0 credits, paid plans only)
Prefetch Brand Data by Email	Work email address	Queued confirmation	`POST /utility/prefetch` (0 credits, paid plans only)
Custom API Request	HTTP method, URL or path, optional query, headers, and body JSON	Raw API response	Any Context.dev endpoint; see below

A few things to know before you build:

No triggers. Context.dev does not fire events into Zapier. Bring the trigger from another app and chain a Context.dev action after it.
Shared optional fields. Every action accepts Timeout MS (up to 300000). The brand lookups also accept Force Language and Max Speed, with the same meaning as the API parameters.
Free and disposable emails are rejected. The email-based actions return a 422 for addresses at Gmail, Yahoo, and similar providers, or at disposable-email domains.
Prioritize is a leftover field. The Screenshot and Styleguide actions still show a Prioritize input. The API has since dropped this parameter, so the field has no effect. Leave it blank.
Some help text says Brand.dev. That is the API’s former name. It is the same API and the same key.

Common trigger pairings

Trigger source	Typical pairing
Typeform “New Form Entry”	Enrich the submitted email or domain
HubSpot “New Contact”	Enrich the contact with logo, industry, and socials
Google Sheets “New Spreadsheet Row”	Bulk-enrich a list of domains
Gmail “New Email” or Email Parser	Pull the sender’s domain and enrich
Webflow / Tally	Capture a domain from a form
Schedule by Zapier	Re-screenshot or re-extract products on a cadence
Email by Zapier	Quickest manual-trigger setup for testing

Setup walkthrough

Trigger fires, Context.dev resolves a brand, the response flows into the destination app.

Prerequisites

A Zapier account (free tier works for testing)
A Context.dev account and an API key from the dashboard (prefix ctxt_secret_)
A Zapier-supported trigger source (for testing, Email by Zapier works without external setup)

1. Install the Context.dev Zapier app

Open the Context.dev Zapier listing and click Connect. Zapier prompts for the API key. Paste your ctxt_secret_* key from the Context.dev dashboard, then give the connection a name (e.g. “Context.dev (production)”) so you can distinguish it from staging keys later. You only do this once per Context.dev account. Every Zap that uses Context.dev re-uses the saved connection.

2. Add a trigger

Create a new Zap and pick a trigger that fires on the event you care about. For testing without any other integration, use Email by Zapier > New Inbound Email:

Pick Email by Zapier as the trigger app.
Pick New Inbound Email as the trigger event.
Zapier generates an inbox address like [email protected]. Note it.
Click Test trigger. Zapier waits for an inbound message.
Send an email to the Zapier inbox address from step 3 with a domain in the subject line (e.g. test stripe.com). Zapier should detect it.

For production, swap in a real trigger: Typeform “New Submission”, HubSpot “New Contact”, Google Sheets “New Spreadsheet Row”, whatever fires on the event you want to enrich.

3. Add the Context.dev action

After the trigger, click + and add an action. Search for Context.dev and pick the action that matches what your trigger gives you. There is no input-type dropdown: each lookup is its own action, so choose Retrieve Brand Data by Domain, by Company Name, by Email Address, or by Stock Ticker based on the field you have. For Retrieve Brand Data by Domain, configure:

Domain: Map the value from the trigger (e.g. the domain parsed from a Typeform submission)
Force Language, Max Speed, Timeout MS: Leave blank unless you need them

Click Test step. Zapier hits Context.dev and shows the parsed response. A first call may require cold crawl work; later calls can reuse a warm cache and are generally faster.

4. Test and publish

Click Test & Review to run the whole Zap end-to-end. Verify every step turns green, then give the Zap a descriptive name and toggle it On. Watch the first few real runs in Zap History: it’s the fastest way to spot mapping mistakes before they pile up.

Sample response

Every brand lookup returns the standard brand envelope. Downstream Zap steps reference fields by path (e.g. 2. Retrieve Brand Data by Domain: Brand Title):

{
  "status": "ok",
  "code": 200,
  "brand": {
    "domain": "loom.com",
    "title": "Loom",
    "description": "Loom is a video messaging platform that enables users to record their screen, camera, or both, to communicate more effectively. Now part of Atlassian.",
    "slogan": "Empowering everyone to communicate more effectively, wherever they are",
    "colors": [
      { "hex": "#040404", "name": "Armor Wash" },
      { "hex": "#655ef3", "name": "Blue Hepatica" }
    ],
    "logos": [
      {
        "url": "https://media.brand.dev/660ae867-d4a1-4c38-a815-6dbc1ceb33d5.svg",
        "mode": "light",
        "type": "logo",
        "resolution": { "width": 150, "height": 48, "aspect_ratio": 3.13 }
      }
    ],
    "socials": [
      { "type": "linkedin", "url": "https://linkedin.com/company/useloom" },
      { "type": "x", "url": "https://x.com/loom" }
    ],
    "industries": {
      "eic": [{ "industry": "Technology", "subindustry": "Software (B2B)" }]
    },
    "links": {
      "blog": "https://loom.com/newsroom",
      "pricing": "https://loom.com/pricing",
      "contact": "https://loom.com/connect/enterprise"
    },
    "address": {
      "street": "140 2nd Street",
      "city": "San Francisco",
      "country_code": "US",
      "postal_code": "94105"
    }
  }
}

Reshape responses with Code by Zapier

Most destination apps want flat fields. Add a Code by Zapier > Run Python step between the Context.dev action and the destination action.

One-shot flatten (most-used)

When you want every common field as a flat output:

import json

status = input_data.get("status", "")
brand = json.loads(input_data.get("brand") or "{}")

logos   = brand.get("logos", []) or []
colors  = brand.get("colors", []) or []
socials = brand.get("socials", []) or []
links   = brand.get("links", {}) or {}
stock   = brand.get("stock", {}) or {}
address = brand.get("address", {}) or {}
eic     = brand.get("industries", {}).get("eic", []) or []

socials_by_type = {s.get("type", "").lower(): s.get("url", "") for s in socials}
light_logo = next((l.get("url") for l in logos if l.get("mode") == "light"), None)
icon_logo  = next((l.get("url") for l in logos if l.get("type") == "icon"), None)

output = {
    "company_name":  brand.get("title", ""),
    "domain":        brand.get("domain", ""),
    "description":   brand.get("description", ""),
    "logo_url":      light_logo or (logos[0].get("url") if logos else ""),
    "icon_url":      icon_logo or "",
    "primary_color": colors[0].get("hex", "") if colors else "",
    "linkedin":      socials_by_type.get("linkedin", ""),
    "twitter":       socials_by_type.get("x", ""),
    "industry":      eic[0].get("industry", "") if eic else "",
    "subindustry":   eic[0].get("subindustry", "") if eic else "",
    "ticker":        stock.get("ticker", "") or "",
    "city":          address.get("city", "") or "",
    "country_code":  address.get("country_code", "") or "",
    "pricing_url":   links.get("pricing", "") or "",
}
output["enrichment_ok"] = status == "ok" and bool(brand.get("title"))

Best logo for a given UI

brand.logos[] is an array of variants. Pick one by type (icon vs. full wordmark) and mode (light, dark, opaque):

import json

brand = json.loads(input_data.get("brand") or "{}")
logos = brand.get("logos", [])

def find(type_, mode):
    return next((l.get("url") for l in logos
                 if l.get("type") == type_ and l.get("mode") == mode), None)

output = {
    "logo_light": find("logo", "light"),
    "logo_dark":  find("logo", "dark"),
    "icon_light": find("icon", "light"),
    "icon_dark":  find("icon", "dark"),
    "logo_any":   logos[0].get("url") if logos else None,
}

Destination	Use
White-background email template	`logo_light`
Dark Slack notification	`logo_dark`
Round avatar bubble in a CRM	`icon_light` (or `icon_dark`)
Anything else	`logo_any`

Detect a missing or weak response

A no-brand result (HTTP 400, error_code: "NOT_FOUND" or "WEBSITE_ACCESS_ERROR") or a server error (HTTP 500) comes back without a usable brand. Branch on it before writing to the destination:

import json

status = input_data.get("status", "")
brand = json.loads(input_data.get("brand") or "{}")

output = {
    "enrichment_ok": status == "ok" and bool(brand.get("title")),
    "status":        status,
    "has_logo":      bool(brand.get("logos")),
    "has_industry":  bool(brand.get("industries", {}).get("eic")),
    "company_name":  brand.get("title", ""),
}

Add a Filter by Zapier step after this: “Only continue if enrichment_ok is true.” The Zap silently skips records that didn’t enrich.

Call any endpoint with Custom API Request

The Custom API Request action sends an authenticated HTTP request using your saved Context.dev connection. Use it for endpoints that don’t have a dedicated Zapier action yet: Markdown scraping, web search, SIC codes, people enrichment, and anything added to the API after the Zapier app was last updated.

Field	What to enter
Method	`GET`, `POST`, or another HTTP method
URL or Path	A full URL such as `https://api.context.dev/v1/web/scrape/markdown`, or a path such as `/v1/web/scrape/markdown`
Base URL	Used only when you enter a path. Defaults to `https://api.brand.dev`, the API’s former hostname, which still works. Set it to `https://api.context.dev` to match these docs.
Query JSON	Query parameters as a JSON object, e.g. `{"url": "https://stripe.com/pricing", "useMainContentOnly": true}`
Headers JSON	Extra headers as a JSON object. `Authorization` is added for you and overrides anything you set here.
Body JSON	Request body as a JSON object or array. Ignored for `GET` requests.
Throw on non-2xx	Turn on so a failed API call fails the Zap step instead of passing an error body to later steps.

Example: scrape a pricing page to Markdown after a competitor is added to a Google Sheet.

Trigger: Google Sheets “New Spreadsheet Row” with a pricing_url column
Action: Context.dev “Custom API Request”
- Method: GET
- URL or Path: https://api.context.dev/v1/web/scrape/markdown
- Query JSON: {"url": "<pricing_url from step 1>", "useMainContentOnly": true}
- Throw on non-2xx: on
Action: Notion “Create Page” with the returned markdown field as the page body

Parameter names and response shapes for every endpoint are in the API reference.

Example automations

Enrich a new HubSpot contact

Trigger: HubSpot “New Contact”
Action: Context.dev “Retrieve Brand Data by Email Address” with the contact’s email
Code by Zapier: One-shot flatten
Filter: Continue only if enrichment_ok is true
Action: HubSpot “Update Contact” with logo, industry, LinkedIn, and address fields

Slack notification with brand context

Trigger: Stripe “New Customer”
Action: Context.dev “Retrieve Brand Data by Email Address” with the customer’s email
Code by Zapier: Best logo for a given UI (use logo_dark for dark Slack themes)
Action: Slack “Send Channel Message” with company name in the title, dark logo as icon, industry in attachment text

Bulk-enrich a Google Sheet

Trigger: Google Sheets “New Spreadsheet Row” with a domain column
Action: Context.dev “Retrieve Brand Data by Domain”
Code by Zapier: One-shot flatten
Action: Google Sheets “Update Spreadsheet Row” with logo, industry, LinkedIn, and pricing-page columns

NAICS-tag a CRM lead

Trigger: Salesforce “New Lead”
Action: Context.dev “Retrieve NAICS Code for Any Brand” with the lead’s domain
Code by Zapier: Pull codes[0].code for the highest-confidence NAICS
Action: Salesforce “Update Lead” with the NAICS code in a custom field

Visual transaction enrichment

Trigger: Plaid webhook
Action: Context.dev “Identify Brand From Transaction Data” with the raw descriptor plus optional MCC, city, and country
Code by Zapier: Pull brand name and logo
Action: Notion “Create Page” with merchant logo, name, and category

Warm the cache before onboarding

Trigger: Typeform “New Form Entry” on your demo-request form
Action: Context.dev “Prefetch Brand Data by Email” with the submitted work email (0 credits)
Action: Calendly or Google Calendar “Create Event” for the demo

By the time your team opens the account in your CRM, the brand lookup is already warm and returns in well under a second.

Weekly product catalog snapshot

Trigger: Schedule by Zapier “Every Week”
Action: Context.dev “Extract Products From a Brand’s Website” with a competitor’s domain and Max Products set to 12
Looping by Zapier: Iterate over products
Action: Airtable “Create Record” per product with name, price, currency, and product URL

Pricing page screenshot to Slack

Trigger: Schedule by Zapier “Every Day”
Action: Context.dev “Take Screenshot of Website” with the competitor’s domain, Page set to pricing, and Full Screenshot set to true
Action: Slack “Send Channel Message” with the returned screenshot URL as an image attachment

Troubleshooting

“Authentication failed.” The API key was rejected. Re-paste it in Zapier’s My Apps > Context.dev connection settings; confirm the ctxt_secret_ prefix.
Email action returns 422. The address is at a free provider (Gmail, Yahoo, and similar) or a disposable-email domain. Filter those out before the Context.dev step, or fall back to Retrieve Brand Data by Company Name.
Prefetch action fails on a free account. Both prefetch actions require a paid plan. Upgrade in the dashboard or drop the prefetch step; every other action works on any plan.
Action returns 408 (“timeout”). Cold-hit timeout on a domain Context.dev hadn’t crawled before. Re-run, or raise Timeout MS; the second hit will be warm.
Custom API Request returns 404. Check the path starts with /v1/ and that the method matches the API reference. Scrape endpoints are GET with parameters in Query JSON, not Body JSON.
No logo in the response. A few brands haven’t published a logo Context.dev could capture. Use Logo Link as a fallback (https://logos.context.dev/?publicClientId=brandLL_xxx&domain=...) for a generated monogram.
The action list or help text says Brand.dev. Brand.dev was the API’s former name. Nothing else changes: same connection, same key, same endpoints.

Next steps

Make integration

The Zapier alternative when you need branching logic and built-in error handling.

Brand API reference

The underlying endpoints. Useful when reading Zap test responses.

Industry classification

EIC vs NAICS vs SIC: when each one fits.

Troubleshooting

HTTP status codes, retry strategies, and common error patterns.

Need help implementing a specific Zap? Email us and we’ll walk through it with you.

Get Started

Give it to your Agent

What can Context.dev do

Optimizations

Integrations

Install the Context.dev Zapier app

What you get

Search actions

Write actions

Common trigger pairings

Setup walkthrough

Prerequisites

1. Install the Context.dev Zapier app

2. Add a trigger

3. Add the Context.dev action

4. Test and publish

Sample response

Reshape responses with Code by Zapier

One-shot flatten (most-used)

Best logo for a given UI

Detect a missing or weak response

Call any endpoint with Custom API Request

Example automations

Enrich a new HubSpot contact

Slack notification with brand context

Bulk-enrich a Google Sheet

NAICS-tag a CRM lead

Visual transaction enrichment

Warm the cache before onboarding

Weekly product catalog snapshot

Pricing page screenshot to Slack

Troubleshooting

Next steps

Make integration

Brand API reference

Industry classification

Troubleshooting

Install the Context.dev Zapier app

​What you get

​Search actions

​Write actions

​Common trigger pairings

​Setup walkthrough

​Prerequisites

​1. Install the Context.dev Zapier app

​2. Add a trigger

​3. Add the Context.dev action

​4. Test and publish

​Sample response

​Reshape responses with Code by Zapier

​One-shot flatten (most-used)

​Best logo for a given UI

​Detect a missing or weak response

​Call any endpoint with Custom API Request

​Example automations

​Enrich a new HubSpot contact

​Slack notification with brand context

​Bulk-enrich a Google Sheet

​NAICS-tag a CRM lead

​Visual transaction enrichment

​Warm the cache before onboarding

​Weekly product catalog snapshot

​Pricing page screenshot to Slack

​Troubleshooting

​Next steps

Make integration

Brand API reference

Industry classification

Troubleshooting

What you get

Search actions

Write actions

Common trigger pairings

Setup walkthrough

Prerequisites

1. Install the Context.dev Zapier app

2. Add a trigger

3. Add the Context.dev action

4. Test and publish

Sample response

Reshape responses with Code by Zapier

One-shot flatten (most-used)

Best logo for a given UI

Detect a missing or weak response

Call any endpoint with Custom API Request

Example automations

Enrich a new HubSpot contact

Slack notification with brand context

Bulk-enrich a Google Sheet

NAICS-tag a CRM lead

Visual transaction enrichment

Warm the cache before onboarding

Weekly product catalog snapshot

Pricing page screenshot to Slack

Troubleshooting

Next steps