Swordfish AI
Sales IntelligenceFind work and mobile phone numbers, emails, and social profiles for a person with the Swordfish AI Search Person API. Agents complete a contact record before outreach spends a touch on a guess.
What This Integration Enables
Swordfish AI is not an email finder that also returns phones. It is a phone product, and the whole shape of the connector follows from that. Search Person returns work and mobile phone numbers, email addresses and social profiles for a person, from whatever identifier you already hold. That identifier can be a social profile on its own, an email on its own, a phone on its own, or a first and last name paired with a website, company, title, email, phone, or a US street plus zip code. Supply exactly one value per data point, since multiple emails or phones in a single request are rejected. The practical consequence is that Swordfish resolves in whichever direction you happen to be travelling, which is what you want when the input is an inbound call, a scraped profile link or a half-filled CRM record.
Two design details make it usable inside an agent rather than just inside a browser tab. Summary Only returns what contact data exists without spending a full credit, so a flow can check before it buys, and Required Data filters results to particular contact types when you only care about a mobile or only care about an email. Note that Required Data is ignored while Summary Only is on, so the two are used in sequence rather than together. The other detail is Get History, which returns a paginated log of previous Search Person requests and their outcomes at 100 rows per page, filterable by date range, by whether the request produced a result, or by a specific request ID. That log is an audit surface. For a category where the reasonable question from a contact is where you got their number, being able to answer which lookup produced it and when is worth more than another data field. Swordfish also enforces a weekly fair-use ceiling on top of the credit balance, surfaced as an Exceed limit credit error, so Get Balance is necessary but not sufficient as a spend guard.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Two-pass lookups on a scraped list
A research pass produces profile URLs for a target account list. Rather than paying full price to discover which ones carry a mobile, the agent runs Search Person with Summary Only across the list first, reading back which contact types exist per person at reduced cost. It re-runs the full lookup only where the summary shows the data the play requires, then creates the contacts in HubSpot with the work line, the mobile, the email and the social profiles written to separate fields. The list that reaches the rep is smaller and every record on it carries what the play needs.
Attributing an inbound signal
A call comes in from a number nobody recognises, or a form arrives with an email and no company. The agent calls Search Person with that single identifier, since a phone alone or an email alone is a valid input combination, and resolves the person, their employer and their social profiles. Because Swordfish accepts a social profile in several formats, including a bare handle notation, an agent can also work from a fragment captured out of a note field. The rep calling back knows who they are calling.
Spend and concurrency handled as flow design
Swordfish limits a key to 5 concurrent requests and applies a weekly fair-use ceiling separate from credits. The agent respects both: it paces a batch rather than fanning out across it, checks Get Balance before starting and posts a Slack alert when the balance falls below the run's requirement, and treats an Exceed limit credit error as a pause-and-notify condition rather than a retry loop. Get History then reconciles what was actually spent against what was expected, without re-running a single lookup.
Human-in-Loop Highlight
Swordfish returns work numbers and mobile numbers, and the distinction is the whole point of the gate. A work line rings a desk inside a business the person chose to be reachable at. A mobile rings a device in their pocket, and the record does not tell you whether that handset is company issued or their own, whether they are in a jurisdiction where a cold call to it needs a prior basis, or whether they are on a do-not-call register somewhere the connector cannot see. An agent can find the number. It cannot make that judgement, and treating both number types as one phone field is how a team ends up cold calling personal mobiles without ever deciding to. So the agent lays the choice out: "[Contact] at [Account] resolved. Work line [number], mobile [number], email [address], [N] social profiles. Lookup request ID [id] recorded in history. Which channel should this contact be approached on?" The rep answers per contact. Emails and work lines are ordinary business contact. A personal mobile is a decision somebody should be able to point to afterwards, which is exactly why Get History and the human-in-the-loop step belong in the same flow.
Agent Capabilities
3 actionsContact Search
1- Search Person Looks up a person's work and mobile phone numbers, email addresses and social profiles from whatever identifiers you already hold. Supply exactly one value per data point, since multiple emails or phones in a single request are not accepted. Valid combinations are a social profile on its own, an email on its own, a phone on its own, or first and last name paired with a website, company, title, email, phone, or US street plus zip code. Use Required Data to insist the result contains particular contact types, or Summary Only to check what exists before spending a full credit.
Account
2- Get Balance Returns the remaining credit balance for the API key. Used to gate a bulk enrichment run or to raise an alert when credits fall below a threshold. Swordfish also enforces a weekly fair-use ceiling separate from the balance, surfaced as an Exceed limit credit error on lookups.
- Get History Returns a paginated history of previous Search Person requests and their outcomes, 100 rows per page. Filter by date range, by whether the request produced a result, or by a specific request ID taken from a Search Person response. Used to audit credit consumption, and to re-read past lookups without spending again.
Frequently Asked Questions
What can FlowRunner do with Swordfish AI?
FlowRunner agents can run Search Person, Get Balance, and Get History in Swordfish AI.
Does connecting Swordfish AI to FlowRunner require OAuth?
No. Swordfish AI connects to FlowRunner with an API key, no OAuth flow required.
Can Swordfish AI trigger a FlowRunner workflow automatically?
Swordfish AI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Swordfish AI
$100 in credits. No card required. Connect in minutes.