Zapier

Overview

Use Zapier to connect FYND to the tools you already use, so scans can be triggered automatically from your existing workflows. In practice, you pick any Zapier trigger (from a CRM, form, spreadsheet, webhook, and so on), then add FYND as the next step to start a security scan as soon as that trigger happens.

To connect FYND, you will need a FYND API key. If you need a refresher on where to create one, see the Partner Portal guide.

Capabilities

FYND’s Zapier connector lets you trigger security scans as part of a Zap, using the data that already exists in your systems. Once your Zap runs, Zapier sends the lead or submission details to FYND and FYND starts the scan automatically. Treat FYND as the “scan step” in your process so your team does not need to leave the tools they already use.

The FYND Zapier connector currently supports one event: Trigger Security Scan. The scan requires a Domain and a valid Email. You can also send extra context like contact name, company name, and phone, but those are optional.

FYND validates email format. During testing, some Zaps may send a placeholder value like email, which will fail validation and prevent the scan from triggering. Using a real sample record in Zapier testing usually resolves this.

Supported flows

• New lead scan – Trigger a scan when a new lead or contact is created in your CRM, or when a form submission comes in with a domain.
• Pipeline or stage based scan – Trigger a scan when a deal or lead reaches a specific stage, so you only scan the leads you care about.
• Spreadsheet driven scans – Trigger scans from Google Sheets or Airtable by mapping domain and email fields from each new row.
• Webhook or internal system scans – Trigger scans from your own systems by using webhooks and passing the domain and email through to FYND.