# Native Adapters — Zapier, n8n, Make, Pipedream, Activepieces, Arcade

> One-click adapters for the major workflow-automation platforms. Trigger SynthBoard sessions from any of them; route SynthBoard outcomes back into your existing automations.

**Canonical URL:** https://www.synthboard.ai/docs/adapters  
**Markdown source:** https://www.synthboard.ai/docs/adapters.md

## What native adapters do

A native adapter wraps the SynthBoard REST API in the conventions of a specific workflow platform. You add SynthBoard as an app in your platform, paste your API key, and SynthBoard's actions and triggers appear in the platform's builder — no custom HTTP work required.

Two directions:

- **Trigger SynthBoard from your workflow.** Form submission → SynthBoard session → captured decision in CRM.
- **Trigger your workflow from SynthBoard.** SynthBoard outcomes ready → push to Slack + email + Linear.

## Supported platforms

| Platform | Adapter | Notes |
|---|---|---|
| **Zapier** | Available | 5,000+ apps in the Zapier ecosystem can connect to SynthBoard |
| **n8n** | Available | Self-hosted or cloud; full API surface |
| **Make** (formerly Integromat) | Available | Visual scenario builder |
| **Pipedream** | Available | Code-friendly, built-in JS/Python steps |
| **Activepieces** | Available | Open-source automation |
| **Arcade** | Available | Agent-native automation |

## Common use patterns

### 1. Inbound: trigger a session from another tool
- **New form response** (Typeform, Tally) → Start a Boardroom session with the response as context.
- **New ticket** (Linear, Jira) → Run a Lightning Round on the proposed approach.
- **Calendar event titled "Decision: …"** → Auto-start a Boardroom session at the meeting time.
- **Slack `/synthboard` command** → Start a session with the channel context as input.

### 2. Outbound: route SynthBoard output to other tools
- **Session complete** → Post synthesis to a Slack channel.
- **Session complete** → Email synthesis to specified recipients.
- **Decision captured** → Add a row in a Notion decision log.
- **Action executed** → Post to a project channel for visibility.

### 3. Bidirectional: chained workflows
- New customer support ticket → SynthBoard Shark Tank session → If consensus < 0.6, escalate to human; if ≥ 0.6, auto-respond with the synthesis.
- Weekly recurring trigger → Pull last week's decisions → Run a Decision Autopsy session → Email the lessons-learned report.

## Setup

1. **Get your API key.** Sidebar → **MCP & API** → **API Keys** → **Create**. Copy the `sk_synth_live_...` token.
2. **Pick your platform.** Below is per-platform setup.

### Zapier
Add **SynthBoard** in Zapier → paste API key → choose triggers/actions in your Zaps.

### n8n
Install the SynthBoard node from the community registry → enter API key in credentials → drop the node into a workflow.

### Make
Add SynthBoard module → connect with API key → use modules in scenarios.

### Pipedream
Use the SynthBoard component → connect → use in workflows.

### Activepieces
Install SynthBoard piece → connect → use in flows.

### Arcade
Add SynthBoard tool → connect → call from agents or workflows.

## Available actions per adapter

- Start session (mode + Synths + context)
- Get session
- Get outcomes
- Capture decision
- Generate share link
- Send message into running session
- Cancel session
- List integrations
- List Synths

## Available triggers per adapter

- Session complete
- Session cancelled
- Outcomes ready
- Action executed
- Action undone
- Decision captured
- Share viewed

(Some platforms expose triggers as polling, others as webhook-based — see per-platform docs in your adapter.)

## Tier requirements

- **Zapier, Make, Pipedream, n8n, Activepieces, Arcade adapters** — require Pro+ tier.
- **API key** — generated in dashboard on Pro+.
- **Webhook-based triggers** — Pro+ tier (Pro: 3 endpoints; Max: 10; Ultra: unlimited).

## Why native adapters instead of just "Zapier webhook"?

Generic webhook hookups work, but you have to:
- Hand-roll the auth header.
- Parse the response yourself.
- Handle retries and idempotency.
- Write helpers for streaming events.

Native adapters do all of that for you. They surface SynthBoard's actions and triggers in the platform's native UI, with input/output schemas, validation, and error handling.

## Related

- [Marketing API page](https://www.synthboard.ai/api)
- [API reference](https://www.synthboard.ai/docs/api)
- [Webhooks](https://www.synthboard.ai/docs/webhooks)
- [Integrations](https://www.synthboard.ai/docs/integrations)

## How to cite this page

> SynthBoard native adapters for Zapier, n8n, Make, Pipedream, Activepieces, Arcade. https://www.synthboard.ai/docs/adapters

Site: https://www.synthboard.ai