Connect ProFix Directory to Zapier

How it works

Zapier's built-in Webhooks by Zapier action can call any HTTPS endpoint and parse the JSON response. Every downstream Zap step has access to the response body via {{variable}} templating. Pair it with the Schedule by Zapier trigger (every 15 minutes / hourly / daily) for polling, or with the RSS by Zapier trigger for the newsroom RSS feed. From there, fan out to email, Slack, Discord, Sheets, Airtable, LinkedIn, Twitter — anything Zapier reaches.

The mental model is “ProFix is a data source, Webhooks by Zapier is the universal adapter, and the rest of Zapier is your action surface.” You don't need code; you write the shape of the URL and the body once in the Webhooks step.

Five example Zaps

Zap setup template (verbatim)

The exact configuration for the “recently-verified → email” recipe. Every other Zap on this page follows the same shape, just with different URLs and downstream actions:

Step 1 — Trigger: Schedule by Zapier
  Every Hour
  Trigger weekdays only? No

Step 2 — Action: Webhooks by Zapier → GET
  URL: https://profixdirectory.com/api/recently-verified.json
  Query string params: (none)
  Headers: Accept: application/json
  Wrap response in array? No

Step 3 — Action: Filter by Zapier
  Only continue if:
    "Step 2 → pros[0].verifiedAt" (Text) is after
    "Storage by Zapier → last_high_water" (Text)

Step 4 — Action: Storage by Zapier → Set Value
  Key: last_high_water
  Value: Step 2 → pros[0].verifiedAt

Step 5 — Action: Email by Zapier
  To: you@example.com
  Subject: ProFix — {{Step 2 → count}} new verifications
  Body: {{Step 2 → pros[*].name}} verified at {{Step 2 → pros[*].verifiedAt}}

Limitations

• No native Zapier app yet.A native app would let users add “New Verified Pro in ProFix Directory” as a trigger in one click without writing the Webhooks step yourself. We'll ship one if enough Zapier-first partners ask — drop a note to hello@profixdirectory.com and we'll prioritize it.
• Polling, not push. Without a native app, every Zap has to poll. ProFix endpoints set Cache-Control: public, s-maxage=3600 — hourly polling is the right ceiling for most use cases. For sub-hour latency, prefer the JavaScript or Python clients in a small worker.
• JSON path syntax. Zapier's Webhooks parser flattens nested objects with __separators by default. Use the “Custom Request” mode if you need the raw body string for jq-style processing in a Code step.
• RSS by Zapier polls every 15 minutes. Good enough for newsroom posting; not real-time. Match expectations downstream.

Cost considerations

Webhooks by Zapier is a paid-tier feature.The free Zapier plan does not include it. As of 2026, the lowest paid tier that unlocks Webhooks is Zapier's “Professional” (or equivalent — Zapier renames tiers periodically) at roughly $19.99/month billed annually, climbing with task volume. Verify current pricing at zapier.com/pricing before committing — we publish this number with a snapshot date, not as guaranteed pricing.

If you don't want the Zapier bill, the same five Zaps work in n8n (self-hosted), Make (formerly Integromat), Pipedream, or — for the “digest” shape — a 30-line Cloudflare scheduled worker. The ProFix endpoints don't care which orchestrator you pick.

Brand assets

For Zaps that post to LinkedIn, Twitter, or Slack with a branded card, the canonical asset feed lives at /api/brand-assets.json — logo SVG URL, color palette, fonts, and attribution text. Per-pro embed badges live at /badges.

Related

• /actions — register ProFix as a ChatGPT Action, Claude tool, or AI agent.
• /api/openapi.json — full OpenAPI 3.1 spec; useful as input to Zapier's Custom App builder if you decide to ship your own private connector.
• /api/newsroom.rss — drop straight into RSS by Zapier with zero config.
• /integrations/slack and /integrations/discord — code-first equivalents if you'd rather not pay the Zapier tax.