Connect Koji to Zapier: Automate Customer Research Workflows in Minutes

TL;DR: Koji connects to Zapier via its native webhooks and Zapier''s "Webhooks by Zapier" Catch Hook trigger. Set up the integration in under 10 minutes: (1) generate a Catch Hook URL in Zapier, (2) add it as a webhook destination in your Koji study, (3) map the payload fields to actions in any of Zapier''s 6,000+ apps. From there, every completed AI interview can auto-create Notion pages, Linear tickets, Salesforce notes, Airtable rows, Gmail summaries — anything Zapier supports.

Why connect Koji to Zapier

Koji handles the hard part of customer research: recruiting, moderation, transcription, theme analysis, reporting. But customer insights only create value when they reach the team and tool that can act on them. That''s where Zapier fits.

A few high-impact patterns we see Koji teams build:

• Notion research repository — every completed interview becomes a new page in a Notion database, tagged with theme and segment
• Linear ticket creation — when a participant raises a specific pain, auto-file a Linear ticket with the verbatim quote
• Salesforce account enrichment — push interview insights onto the contact''s record in Salesforce so AEs see customer voice mid-deal
• Airtable research CRM — track participants across multiple studies in Airtable with rich metadata
• Slack alerts — though Slack has a native integration, Zapier lets you route only specific interviews (e.g., score above 4 on a scale question) to specific channels
• Email digests — daily or weekly Gmail digests of new completions to stakeholders

Zapier supports 6,000+ apps, so almost any internal workflow can be wired up.

How the integration works

Koji fires a webhook every time an interview completes. The payload includes the study ID, interview ID, completion timestamp, participant metadata, transcript URL, and structured answers. Zapier''s "Catch Hook" trigger receives that payload, parses it into named fields, and exposes those fields to every downstream Zap action.

This is the standard Zapier integration pattern for products without a native Zapier app — and it works just as well. You get the full flexibility of Zapier without waiting for a dedicated integration.

[Customer completes interview]
        ↓
[Koji webhook fires payload]
        ↓
[Zapier Catch Hook receives]
        ↓
[Zap runs your chosen action: Notion / Linear / Salesforce / etc.]

Step-by-step setup (10 minutes)

Step 1: Create a Catch Hook Zap in Zapier

1. In Zapier, click Create Zap.
2. For the trigger app, search Webhooks by Zapier.
3. Choose Catch Hook as the event.
4. Click Continue. Zapier will display a unique URL like https://hooks.zapier.com/hooks/catch/12345678/abcdefg/.
5. Copy that URL. You''ll paste it into Koji next.

If you''re on the free Zapier plan, the basic Webhooks by Zapier trigger is included on paid Zapier plans. For high-volume studies you''ll want a Starter or Professional Zapier subscription.

Step 2: Add the webhook URL to your Koji study

1. In Koji, open your published study and go to the Webhooks section under study settings.
2. Click Add Webhook Destination.
3. Paste the Catch Hook URL.
4. Choose the event you want to subscribe to — usually interview.completed.
5. Save.

Behind the scenes, Koji will now POST the interview payload to that URL each time an interview is completed. For full payload schemas and event types, see the webhook setup guide and research automation webhooks.

Step 3: Trigger a test webhook

Back in Zapier, click Test Trigger. Zapier will wait to receive a payload. In Koji, either complete a test interview yourself or trigger a manual test from the webhook settings page.

Within a few seconds, Zapier will display the received payload — something like:

{
  "event": "interview.completed",
  "interview_id": "int_a1b2c3",
  "study_id": "stu_x9y8z7",
  "completed_at": "2026-05-15T14:32:11Z",
  "participant": {
    "email": "[email protected]",
    "name": "Alex"
  },
  "structured_answers": [
    {"question_id": "q1", "type": "scale", "value": 4},
    {"question_id": "q2", "type": "yes_no", "value": true}
  ],
  "transcript_url": "https://app.koji.so/interviews/int_a1b2c3/transcript",
  "report_url": "https://app.koji.so/studies/stu_x9y8z7/report"
}

Once Zapier sees this payload, every field is available to map into downstream actions.

Step 4: Add your action

Now wire up what should happen on each completion. A few quick examples:

Create a Notion page

• App: Notion → Action: Create Database Item
• Map participant.name → Page Title
• Map transcript_url → URL property
• Map structured_answers[0].value → Score property

Create a Linear ticket (only when score is low)

• Add a Filter step: only continue if structured_answers[0].value is less than 3
• App: Linear → Action: Create Issue
• Title: "Low CSAT from {{participant.name}}"
• Description: paste the transcript URL

Send a Slack message

• App: Slack → Action: Send Channel Message
• Channel: #customer-research
• Message: "New interview from {{participant.name}}. Score: {{structured_answers[0].value}}. Read: {{transcript_url}}"

Append to a Google Sheet

• App: Google Sheets → Action: Create Spreadsheet Row
• Map each structured answer to a column

Step 5: Turn the Zap on

Test once more end-to-end. If the payload routes correctly, flip the Zap to On. Every future completed interview now triggers your automation.

Comparing Zapier to Koji''s native integrations

Koji ships with native integrations for Slack, HubSpot, and direct webhook setup. The native integrations are faster to configure and require zero Zapier subscription.

Zapier is the right choice when:

• You need to route to an app Koji doesn''t have native support for (Notion, Linear, Salesforce, Airtable, Asana, Trello, Pipedrive, ClickUp, Monday, etc.)
• You need conditional routing (filters, branches based on answer values)
• You want to chain multiple actions in one workflow (e.g., create Notion page and file Linear ticket and email the PM)
• Your team already maintains its automations in Zapier and you want consistency

For simple routing to Slack alone, the native integration is faster. For complex multi-app routing, Zapier wins.

Real-world workflow examples

The "PMF Detector" Zap Track every Koji interview with a scale question on pain intensity. If the score is 5/5, file a Linear ticket tagged "PMF candidate" and DM the founder. Used by Koji-powered seed-stage teams to spot signal among 100+ interviews.

The "Customer Quote Wall" Zap Append every interview''s top quote (from the open_ended answer field) into an Airtable base. Marketing pulls from this base for landing page social proof. A new quote candidate appears every time an interview completes.

The "AE Briefing" Zap When a Koji interview is tagged with a specific company domain, push the transcript summary onto that company''s Salesforce account. AEs see the latest customer voice when they open the record.

The "Weekly Discovery Digest" Zap Aggregate the past 7 days of interview completions into a daily-scheduled Zap that emails the product team every Monday with theme counts and links.

Best practices

• Use Zapier''s filter step liberally. Don''t spam Linear with every interview — only the ones that meet a criteria.
• Map structured answers explicitly. Zapier represents the structured_answers array as indexed items. Map by index (and ideally by question_id) so your Zap doesn''t break when you reorder questions.
• Don''t put participant PII into shared channels. Many Zapier destinations (Slack channels, public Notion databases) are visible to your whole team. Strip or hash participant emails in the Zap if needed. See anonymizing customer interview data for the full privacy playbook.
• Monitor Zap history. Zapier shows a log of every run. Check it weekly to catch silent failures.
• Beware of rate limits. Some downstream apps (especially Notion, Airtable) have per-minute write limits. For high-volume studies, batch via Zapier''s Digest or Storage steps.

When to use webhooks directly vs Zapier

Zapier adds latency (typically 1–15 minutes between payload and downstream action) and a per-Zap cost. For high-volume or low-latency workflows, hit the Koji webhook endpoints directly from your own backend. For most teams, Zapier is the right balance of speed-to-setup and flexibility.

Frequently Asked Questions

Do I need a paid Zapier subscription? The free tier supports basic webhooks but limits the number of Zaps and tasks. For production research automation, Zapier Starter or Professional is usually required.

Does Koji have a native Zapier app? Not yet. The Catch Hook pattern described here is the standard integration approach and gives you full Zapier flexibility. A native Zapier app is on the roadmap.

Will Zapier expose participant emails? The webhook payload includes whatever participant info you collected via your intake form. If you want to keep emails out of downstream tools, omit the email field from the intake or strip it inside Zapier using a Formatter step.

Can I trigger Koji actions from Zapier (not just receive from)? Yes — Koji also has a public REST API. You can use Zapier''s "Webhooks by Zapier → Custom Request" action to call Koji endpoints (e.g., starting an interview, importing respondents). See the user research API guide for the available endpoints.

What if my webhook fails to deliver? Koji retries failed deliveries with exponential backoff. The webhook delivery logs in your study settings show all attempts and status codes. For deeper integration debugging, see the webhook setup guide.

Is there an alternative to Zapier? Yes — Make.com (formerly Integromat), n8n (self-hosted), and Pipedream all support the same webhook-receive pattern. The setup is nearly identical: paste the destination tool''s webhook URL into Koji.

Related Resources

• Structured Questions Guide: 6 Question Types Every Koji Study Needs
• Webhook Setup: Configure Koji Webhooks
• Research Automation Webhooks: Build Real-Time Pipelines
• User Research API: Embed AI Interviews into Any Workflow
• Slack Research Insights Integration
• HubSpot Research Integration