Skip to main content
The Influship Make app adds 10 Actions, 3 Searches, and a Universal API module you can drop into any scenario. It doesn’t ship Triggers — your scenario is started by something you track (an Instagram comment, a Slack message, a Google Sheets row), and Influship runs as an enrichment module inside it.

Install

The Make app is in private distribution. Email support@influship.com with your Make account email to be added.
Once you have access, the Influship app appears in the module picker when you build a scenario.

Authenticate

1

Get your API key

From the developer dashboard. Keys start with inf_.
2

Create the connection

In the Make editor, add an Influship module to your scenario. Click Add under Connection, paste your API key, click Save.
3

Verify

Make hits /v1/creators/autocomplete (0.05 credits) to verify the key works. The connection appears in your Connections list as Influship (…abc1) so you can tell multiple accounts apart.

Capabilities

Searches

Actions

Universal

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

Build your first scenario

Recipe — Enrich an Airtable handles list

You keep a research base of Instagram handles; this scenario fills in follower count, engagement, and verified status as new rows are added.
1

Trigger: Airtable — Watch Records

Watch your Creators to Research table for new rows. Output one bundle per new record.
2

Module: Influship — Lookup Profiles

In the Profiles array field, click Add Item and map platform: instagram (hard-coded) and username (from the Airtable bundle’s handle column).The module accepts up to 50 profiles per call. If you’re iterating row-by-row from Airtable you’ll pass one; if you batch with an Aggregator beforehand, you can compress 50 records into a single 0.1×50 = 5-credit call.
3

Module: Airtable — Update a Record

Write followers, engagement_rate, and is_verified back into the same row.
Per-row cost: 0.1 credits = $0.001 unbatched. Batched via Aggregator: 0.002/row at 50-row batches.

Recipe — Score inbound creator pitches

A creator pitches you; Make scores them and routes the winners into a Linear issue.
1

Trigger: Gmail — Watch Emails

Filter inbound mail to your creator outreach inbox.
2

Module: Tools — Match a Pattern

Extract the @handle from the email body with a regex.
3

Module: Influship — Get Profile by Handle

Confirm the handle exists and pull the creator’s profile ID.
4

Module: Influship — Score Creator Match

Pass the creator ID and your stored brief. Returns match_score and a decision of good/neutral/avoid.
5

Router + Filter: decision = good

Use a Router to branch; filter the “good” route on {{decision}} === "good".
6

Module: Linear — Create Issue

On the good branch, file an issue in #partnerships with match_score and reasons in the body.
Per-pitch cost: ~10 credits ($0.10). The match step is the LLM-heavy call.

Cost expectations

Rough monthly spend by volume: The Search Creators and Score Creator Match modules dominate — they run AI inference. Profile and post lookups are effectively free at agency scale.

Troubleshooting

Your key was revoked or rotated. Get a fresh one from the developer dashboard, then in Make go to Connections → Influship → Reauthorize.
Make’s per-module retry honors the Retry-After header on 429 responses — the scenario waits then resumes automatically. If you hit limits constantly, contact support@influship.com to discuss raising them.
Live data modules can return 503 service_unavailable when an upstream platform temporarily throttles a scrape. Treat that as retryable with Retry-After; it is not the same as your Influship account hitting a 429 rate limit.
Metered usage requires a payment method on file. Update it in developer billing — the scenario resumes the next time it runs.
Influship doesn’t emit real-time events. The app is enrichment-only — your scenario is started by something you track (a webhook from Instagram Business, a database change, a calendar event), and Influship runs as a module inside it. A trigger that fires when we happen to re-fetch a creator hours later would create scenarios that miss real events.
Use the Make an API Call Universal module. Set the method, relative path (e.g. /v1/health), query string, and body. The connection’s API key is attached automatically.

Support