n8n + Tevyr

#What you can do

#Pattern 1 — Tevyr → n8n (Tevyr webhook is the trigger)

This is the most common direction. Tevyr fires a webhook on every meaningful event; n8n catches it and runs your workflow.

#Setup

1. In n8n, click New Workflow
2. Click the + to add a node, search Webhook, pick the Webhook trigger node
3. Set HTTP Method to POST
4. Set Path to something descriptive (e.g. tevyr-session-events)
5. Set Response Mode to Immediately — this returns 200 to Tevyr without waiting for downstream nodes to finish. Critical for low-latency macro fires; see Troubleshooting below.
6. Click Listen for Test Event to capture a real Tevyr payload for testing
7. In Tevyr, open Settings → Webhooks for your event
8. Click Add Webhook, paste the n8n Test URL for now, choose which events to send
9. Save. Click Test in Tevyr's webhook panel — n8n captures the payload and shows the fields
10. Add downstream nodes (Slack, Sheets, Postgres, anything)
11. Activate the workflow with the top-right toggle, then swap Tevyr's webhook URL from Test → Production

#Recipe — Q&A submitted → Slack message

1. Trigger: Webhook node (POST /tevyr-session-events)
2. Add node: Slack → Send a message
3. Channel: #qa-moderation
4. Message text — use n8n's expression editor to drop in {{ $json.body.question.text }} and {{ $json.body.question.submitter_name }}
5. Activate the workflow

Every Q&A submission now lands as a Slack ping with the question text and the submitter's name when available.

#Recipe — session.completed → Postgres row

1. Trigger: Webhook node

2. Add node: Postgres → Execute Query

3. Pick or create the credential pointing at your DB

4. Query:

   INSERT INTO session_log (date, title, speaker, planned_sec, actual_sec, overrun_sec)
   VALUES (
     '{{ $json.body.session.completed_at }}',
     '{{ $json.body.session.title }}',
     '{{ $json.body.session.speaker_name }}',
     {{ $json.body.session.duration_seconds }},
     {{ $json.body.session.actual_duration_seconds }},
     {{ $json.body.session.overrun_seconds }}
   )
   

   Copy

Run an event end-to-end — your private DB has a complete log without anyone touching it.

#Recipe — timer.warning → email speaker

1. Trigger: Webhook node
2. Add node: IF — only continue if {{ $json.body.session.speaker_email }} is not empty
3. Add node: Send Email (or Gmail / Microsoft Outlook)
4. Subject: 5 minutes left — please start wrapping up
5. Body: Hi {{ $json.body.session.speaker_name }}, the timer just hit your warning threshold. About {{ $json.body.remaining_seconds }} seconds remaining.

Useful for remote speakers on Zoom who can't see a confidence monitor.

#Pattern 2 — n8n → Tevyr (n8n workflow calls Tevyr's API)

The reverse direction. n8n triggers off something else (Calendly, Notion, a cron schedule, anything in its catalog) and uses Tevyr's API to take action.

#Setup

1. In n8n, New Workflow
2. Set the trigger to whatever app you're listening to (e.g. Calendly Trigger → Invitee Created)
3. Add the next node: HTTP Request
4. Method: GET
5. URL: the Tevyr API endpoint (recipes below)
6. Drop in query parameters with n8n expressions to map the trigger app's fields

#Recipe — Calendly booking → create Tevyr session

1. Trigger: Calendly Trigger → Invitee Created
2. Action: HTTP Request
3. URL: https://api.tevyr.com/v1/session/create
4. Query parameters:
   • room_id: your Tevyr room ID
   • api_key: your Tevyr API key
   • title: {{ $json.event_type.name }}
   • speaker_name: {{ $json.invitee.name }}
   • duration_seconds: {{ $json.event.duration }}
   • scheduled_start_time: {{ $json.event.start_time }}

Every Calendly booking auto-creates a Tevyr session. Open the controller — your day's lineup is already loaded.

#Recipe — Schedule trigger → fire a Tevyr macro every Monday morning

1. Trigger: Schedule Trigger → cron 0 9 * * 1 (every Monday 9am)
2. Action: HTTP Request → GET https://api.tevyr.com/v1/macros/run?macro_id=YOUR_MACRO_ID&room_id=YOUR_ROOM_ID&api_key=YOUR_API_KEY

A recurring weekly cue fires from n8n with no human in the loop.

#Pattern 3 — Tevyr macro fires a workflow (native template path)

Use this when you want a Tevyr macro step to fire an n8n workflow inline — branch on the timer, the session, or prior step output before firing. Faster than the webhook fan-out path and the macro builder gives you per-fire field interpolation against {{ctx.*}}.

#Setup

1. In n8n, New Workflow → add a Webhook trigger node, set POST, give it a path, set Response Mode to Immediately
2. Activate the workflow with the top-right toggle
3. Copy the Production URL (NOT the Test URL — the Test URL only listens while the editor is open)
4. In Tevyr, Settings → Integrations → Add new → n8n, paste the URL, name the connection (e.g. "n8n — speaker reminder"), click Save

The URL format depends on where your n8n lives:

#Verify the wiring

1. Click Test on the new Tevyr connection — Tevyr POSTs a test payload to your n8n webhook URL
2. Open the workflow's Executions tab — the test run should appear with the full Tevyr payload
3. Finish wiring downstream nodes

#Use the connection in a macro

1. Drag flow.http_request into any macro
2. Pick your n8n connection from the dropdown
3. Pick the Fire workflow action
4. Fill the fields:

#Payload shape n8n receives

Every fire ships this body:

{
  "event": "session_started",
  "message": "Round 1 just started at 4:24 PM",
  "extra": { "speaker": "Round 1", "remaining": 1741 },
  "ctx": {
    "session_name": "Round 1",
    "event_name": "Boxing Rounds",
    "timer_remaining": 1741,
    "now_iso": "2026-05-16T04:24:18.442Z"
  }
}

In the workflow, this body shows up as {{ $json.body.event }}, {{ $json.body.ctx.session_name }}, etc. Use a Switch or IF node to branch on event for routing, and pull structured values from extra and ctx for downstream actions.

#Common payload reference

When Tevyr fires a webhook, the payload includes structured fields you can map in n8n. Below are the most-used field paths for each event type:

In n8n expressions these are accessed as {{ $json.body.<path> }} (the webhook body is wrapped in a top-level body field by the Webhook node).

See the Webhooks reference for the full payload shape of every event type.

#Troubleshooting

#"Workflow doesn't trigger when Tevyr fires"

• 95% of the time this is Test URL vs Production URL. The Test URL only listens while the workflow editor is open and Listen for Test Event is active. For long-running production wiring, you need the Production URL and the workflow must be activated with the top-right toggle.
• Check the workflow's Executions tab. If failed executions land there with a 500, n8n received the request but a node failed — debug from there.
• If nothing lands in Executions, n8n never received the request. Check Tevyr's webhook delivery log for the response code.

#"Self-hosted instance behind a firewall"

• For Tevyr → n8n webhooks to work, your n8n instance must be reachable from the public internet. Behind-NAT or private-VLAN deploys won't receive the request.
• Options: expose via Cloudflare Tunnel, ngrok, or a reverse proxy; or move to n8n Cloud; or run a public-facing relay (e.g. a Cloudflare Worker that re-POSTs to a private n8n).

#"n8n returns 500 on receive"

• The Webhook trigger node's Response Mode matters:
  • Immediately — n8n returns 200 as soon as the webhook is received, then runs the workflow async. Use this for Tevyr macro fires; it minimizes the round-trip and Tevyr doesn't care about the workflow result.
  • When Last Node Finishes — n8n waits for the entire workflow to complete before responding. For long workflows this exceeds Tevyr's HTTP timeout and Tevyr marks the delivery failed.
• For Pattern 3 (macro fires), Response Mode must be Immediately.

#"Authentication on the webhook node"

• n8n's Webhook node has an optional Authentication field — Basic Auth, header auth, or none. If you enable it, encode the credential into the URL pasted into Tevyr:
  • Basic Auth: https://user:pass@your-n8n.example.com/webhook/<id>
  • Header auth: not directly supported by Tevyr's URL field — leave Authentication on None for catch-hook use cases.

#Context variables

When Tevyr → n8n via a macro step (using the n8n template or Generic HTTP), the body fields support {{ctx.*}} interpolation. n8n receives whatever fields you stitched in. See the full context-variable reference. Common ones: {{ctx.event.title}}, {{ctx.session.title}}, {{ctx.session.speaker_name}}, {{ctx.timer.remaining_seconds}}, {{ctx.now.iso}}.

#Triggered by webhook events

For the inverse — fire a workflow on every Tevyr event — use a webhook in Integration mode with your n8n connection, OR use URL mode and paste the n8n Production URL directly. Both work; integration mode is friendlier when you have multiple workflows to manage.

#Related

• Zapier — alternative catch-hook pattern with a larger app catalog
• Make — alternative catch-hook pattern with a visual scenario builder
• Macros — fire an n8n workflow from a specific macro step (mid-show, conditional, etc.)
• API reference — every endpoint n8n can call
• Webhooks — every event Tevyr can fire
• Integrations Overview — other tools you can wire alongside n8n