Skip to main content
Influship is an enrichment API, not an event source. In a no-code platform, your scenario is started by something you already track — a new Instagram comment, a Slack message, a Google Sheet row, an inbound email — and Influship runs as a step inside that scenario to enrich, score, search, or look up. That model decides which capabilities are exposed: Actions (do work, return data) and Searches (find a single record, used with Find-or-Create). There are no Triggers, because Influship doesn’t emit events that fire on real-world time.

Pick a platform

Zapier

10 Actions + 3 Searches. API-key auth. In Private Beta — email us to be added.

n8n

Community node with 13 operations across 4 resources. Marked usableAsTool, so n8n AI Agents can call it.

Make

10 Actions, 3 Searches, plus a Universal API module. Mirrors the Zapier surface 1:1.

What you can do across all three

The YouTube channel actions accept a bare handle (techreviews), an @handle (@techreviews), or a full channel URL (https://youtube.com/@techreviews) — surrounding share tokens and trailing paths are ignored. A value that isn’t a channel handle returns a 400 validation error.
All three platforms expose the same surface. Pick the one your team already uses.

How costs work

Every call is metered in credits. 1 credit = $0.01.
  • Reads are cheap: profile or post lookups cost 0.05–0.1 credits.
  • AI calls (search, match, lookalike) are pricier: 1.5–25+ credits depending on what they return.
  • Live scrapes (the /v1/raw/* actions) are 0.5 credits regardless of platform.
Each per-platform page lists the cost for every capability so you can budget before you build.

Three workflow patterns that fit Influship

Bulk enrichment

A new row appears in a sheet or CRM → look up the handle → write back metrics.

Inbound scoring

A creator pitches you in email or Slack → score them against your brief → route the good ones into your pipeline.

On-demand discovery

A form submission or slash command → search for matching creators → drop results into Notion, Linear, or Slack.
Each per-platform page walks one of these end-to-end with a concrete recipe.