Skip to main content
The Influship n8n community node adds 13 operations across 4 resources (Creator, Profile, Post, YouTube) to your n8n instance. It’s a single declarative node — pick a resource, pick an operation, fill in the parameters, run. The node is marked usableAsTool: true, so n8n AI Agents can call any of its operations as a tool. There are no trigger nodes — Influship is an enrichment API. Your workflow is started by something you track (an Instagram Business webhook, a Postgres trigger, an inbound email), and Influship runs as a step inside it.

​
Install

  1. Open Settings → Community Nodes.
  2. Click Install and enter @influship/n8n.
  3. Accept the risks of running a community node.
  4. Refresh the editor — the Influship node appears in the actions panel.

​
Authenticate

1

Get your API key

From the developer dashboard. Keys start with inf_.
2

Create the credential

In n8n, go to Credentials → New, search Influship API, paste your key, and click Save.
3

Test

n8n hits /v1/creators/autocomplete (0.05 credits) to verify the key works. If you see a green check, you’re connected.

​
Capabilities

​
Resource: Creator

​
Resource: Profile

​
Resource: Post

​
Resource: YouTube

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

​
Build your first workflow

​
Recipe — Enrich a Postgres row, fan out to Slack

A new lead lands in your creators_to_review table; n8n looks up their Instagram profile, scores them against a stored brief, and posts a Slack summary if the score clears a threshold.
1

Trigger: Postgres Trigger

Watch the creators_to_review table for new rows.
2

Action: Influship — Profile → Get

Map {{$json.handle}} to Instagram Username. Returns follower count, engagement, verified status.
3

Action: Influship — Creator → Score Match

Pass {{$json.id}} (the creator ID you got from the profile lookup, hydrated via Get if needed) and your brief text. Returns match_score (0–1) and decision.
4

IF node: decision === 'good'

Branch on the n8n IF node.
5

Action: Slack — Post Message

On the true branch, post {{$json.creator.username}} scored {{$json.match_score}}: {{$json.reasons[0].text}} to #marketing-leads.

​
Use it from an AI Agent

The node is usableAsTool: true, so any n8n AI Agent (LangChain, OpenAI Tools, etc.) can call Influship operations to answer creator-related questions in a conversation:
Add the Influship node as a tool on your AI Agent node; the agent picks operations based on the user’s request. Bound by your account’s credit limits — keep an eye on cost if the agent gets chatty.

​
Cost expectations

n8n’s polling cadence and “Retry on Fail” defaults mean per-event cost matters more than throughput. A rough budget:

​
Troubleshooting

Your API key was revoked or rotated. Go to Credentials → Influship API → Reconnect and paste a fresh key from the developer dashboard.
n8n’s per-node Retry On Fail setting handles this automatically. The Retry-After header on the 429 response tells n8n how long to wait. If you’re seeing it constantly, your account is at its tier’s rate limit — email support@influship.com.
Live data nodes can return 503 service_unavailable when an upstream platform temporarily throttles a scrape. Use Retry On Fail and honor Retry-After; this is not your API key hitting its Influship account rate limit.
502 upstream_contract_broken means the upstream source returned data Influship could not normalize. Do not use Retry On Fail for this response because the same request will reproduce the failure and may charge another source credit. Stop the workflow or use your last cached value; the failure is automatically reported to Influship.
Almost always means a previous node returned an empty array and you’re accessing $json[0].x. Use the IF node or ?? null to guard.
Influship doesn’t emit real-time events. The node is enrichment-only — your workflow is started by something you track (a Postgres change, an HTTP webhook, a schedule), and Influship runs as a step inside it. A trigger that fires when we happen to re-fetch a creator hours later would create workflows that “missed” real events.

​
Support