> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). The sections below mirror the orientation block in [`/llms.txt`](https://www.socialfetch.dev/llms.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need a structured operation inventory. The catalog covers documented operations with on-site reference pages.

## This page

- **On-site (HTML):** [https://www.socialfetch.dev/docs/integrations/pipedream](https://www.socialfetch.dev/docs/integrations/pipedream)
- **Markdown (.mdx) URL:** [https://www.socialfetch.dev/docs/integrations/pipedream.mdx](https://www.socialfetch.dev/docs/integrations/pipedream.mdx)

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** [https://www.socialfetch.dev/openapi.json](https://www.socialfetch.dev/openapi.json)

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [SDK reference](https://www.socialfetch.dev/docs/sdk-reference.mdx) — exhaustive SDK method inventory and route mapping for agents, tooling, and power users.
- [Choose the right endpoint](https://www.socialfetch.dev/docs/choose-endpoint.mdx) — task-oriented route selection for smoke tests, profiles, list endpoints, and single-item lookups.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — fast comparison of identifiers, pagination, outcomes, media download, and SDK coverage.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, SDK, and REST API connection paths.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 87 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).

---
# Pipedream (https://www.socialfetch.dev/docs/integrations/pipedream)

Use **Social Fetch** in [Pipedream](https://pipedream.com) workflows with API key auth (`sfk_…`). The integration mirrors our [Zapier](/docs/integrations) catalog subset: one polling **New Profile Update** source plus five consolidated actions (profile, post, list posts, transcript, credit balance).

  Components are maintained in this monorepo under `integrations/pipedream/`. Marketplace listing requires a PR to [PipedreamHQ/pipedream](https://github.com/PipedreamHQ/pipedream) after Pipedream registers the app — see [PUBLISHING.md](https://github.com/social-freak-ltd/socialfetch/blob/main/integrations/pipedream/PUBLISHING.md) in the repo.

What you'll need

* A **Pipedream** account.
* A **Social Fetch API key** — create one in your [API Keys](https://app.socialfetch.dev/api-keys) dashboard.
* **Credits** for metered routes — see [Credits & billing](/docs/credits).

Components (v1)

| Type   | Name               | Purpose                                                     |
| ------ | ------------------ | ----------------------------------------------------------- |
| Source | New Profile Update | Poll a profile on a schedule; emit when the payload changes |
| Action | Get Profile        | TikTok, Instagram, Twitter/X, Threads, Facebook, LinkedIn   |
| Action | Get Post           | Post/video/tweet lookup from URL                            |
| Action | List Profile Posts | Recent feed items with optional cursor                      |
| Action | Get Transcript     | Video/post transcript from URL                              |
| Action | Get Credit Balance | Current API credit balance                                  |

Every action maps to the same routes documented in the [API reference](/docs/api).

Connect your API key

1. Add a Social Fetch step to a workflow (after the app is available in the registry).
2. When prompted, paste your full `sfk_…` key from [API Keys](https://app.socialfetch.dev/api-keys).
3. Pipedream validates the connection with `GET /v1/whoami`.

Local development

If you contribute components or test before marketplace merge:

```bash
pd login
pd dev integrations/pipedream/components/socialfetch/sources/new-profile-update/new-profile-update.mjs
```

From the monorepo root, regenerate action shells after catalog changes:

```bash
pnpm generate:pipedream
```

Full API surface

Pipedream v1 intentionally covers the high-traffic workflow paths. For every documented route (Reddit, Spotify, web scrape, and more), use the [REST API](/docs/api), [TypeScript SDK](/docs/sdk), or [n8n node](/docs/integrations/n8n).