Skip to main content
The Influship Zapier integration adds 4 Actions and 2 Searches you can drop into any Zap. It doesn’t ship Triggers — your Zap is started by something you already track (a new message, a spreadsheet row, a form submission, or an inbound email), and Influship runs as a step inside that Zap to enrich, score, or search.
The integration is in Private Beta. Email support@influship.com with the Zapier account you want invited.

Connect your account

1

Add an Influship step to a Zap

In the Zap editor, search for Influship in the action picker and add the action you want.
2

Connect

Click Connect on the Influship step. A modal asks for your API key.
3

Paste your API key

Get your key from the developer dashboard. Keys start with inf_. Paste it, then click Yes, Continue.
4

Done

Zapier validates the key without billing a data lookup, then saves the connection with a short account identifier. Your API key is never included in the displayed label.

Capabilities

Searches

Find Creator returns the best match for a brief and can feed creator-ID fields in later steps. Get Creator by ID returns at most one.

Actions

All costs are in credits. 1 credit = $0.01.

Build your first Zap

Three concrete workflows, all started by Zaps you may already have.

Recipe 1 — Hydrate a saved creator shortlist

You save Influship creator IDs during research; this Zap keeps the corresponding creator records current in your working sheet.
1

Trigger: New Spreadsheet Row (Google Sheets)

Watch a sheet with a creator_id column.
2

Search: Get Creator by ID (Influship)

Map the saved ID into Creator ID. The result includes the creator record and its known profiles.
3

Action: Update Spreadsheet Row (Google Sheets)

Write the creator name, summary, themes, and profile fields you need back into the same row.
Per-row cost: 0.1 credits = $0.001. Hydrating 1,000 saved creators costs about a dollar.

Recipe 2 — Score inbound creator pitches

When a creator emails you, score them against your campaign brief and route the strong matches into a “Worth a meeting” board.
1

Trigger: New Email Matching Search (Gmail)

Filter inbound mail to your creator-outreach inbox.
2

Search: Find Creator (Influship)

Use the creator’s name, niche, and other details from the email as a short search brief. The search returns the best matching creator record.
3

Action: Score Creator Match (Influship)

Score the creator against a stored campaign brief. The action returns match.decision (good, neutral, or avoid) and match.score from 0–1.
4

Filter + Action: Create Card (Trello / Linear / Asana)

Only create the card when match.decision = good. Add match.score and match.reasons to the card body.
Typical per-pitch cost: 28 credits ($0.28).

Recipe 3 — On-demand shortlist via Slack command

Marketing types a brief in Slack; a Notion database fills with ranked candidates.
1

Trigger: New Slash Command (Slack)

Set up /find-creators <brief> in your workspace.
2

Action: Search Creators (Multiple Results)

Pass the slash-command text as the Search Query, set Number of Results to 10.
3

Action: Create Database Item (Notion) — Loop

Loop over the results line items so each creator becomes its own Notion row with score, reasons, and the primary profile.
4

Action: Reply Ephemeral (Slack)

Acknowledge in Slack with a link to the Notion view.
Per-search cost: 25 + (2 × 10) = 45 credits ($0.45).

Cost expectations

A rough sense of monthly spend, assuming typical agency volume: The search and match actions dominate cost — they’re the AI-heavy paths. Hydrating a saved creator record is inexpensive.

Troubleshooting

Your key was revoked or rotated. Get a fresh one from the developer dashboard and reconnect — in Zapier, go to My Connections → Influship → Reconnect.
Your account hit its per-minute rate limit. Zapier reads Retry-After from the response and waits before retrying — no action needed. If you’re hitting limits regularly, contact support@influship.com to discuss raising them.
A live data request was temporarily unavailable. Zapier reads Retry-After from the response and retries automatically. This is different from your Influship account rate limit.
Metered usage requires a payment method on file. Update it in developer billing — the Zap resumes the next time it fires.
Influship doesn’t have real-time post events to emit. The integration is intentionally enrichment-only — your Zap is started by something you track (a source-app webhook, spreadsheet row, form submission, etc.) and Influship runs as an enrichment step inside it. Faking a trigger that fires when we happen to discover a post hours later would create confused Zaps that “missed” real events.
No. The API is read-only — every operation here is GET or query-style POST. Influship doesn’t store your data; it returns what we know about creators.

Support