Generic HTTP + Tevyr

#What you can do

#Prerequisites

• Tevyr Starter plan or above — Free plan ships 0 integration connections
• A target URL that's reachable from the public internet
• Auth credentials if the API needs them (bearer token, basic auth, or a custom header)

#One-time setup

#1. Add the connection

1. Settings → Integrations → Add new
2. Pick the Generic HTTP tile
3. Fill the form:
   • Name — friendly label (e.g. "Make.com webhook", "Linear API")
   • Base URL — the API's root, e.g. https://api.linear.app/graphql or https://hook.make.com/abc123
   • Authentication — pick none, bearer, basic, or header depending on the provider's docs
   • Secret (if not none) — paste the token / password / header value
4. Click Save, then Test — Tevyr makes a GET to the base URL with the auth applied and surfaces whatever the server responds

#2. Use the connection in a macro

1. Drag flow.http_request into any macro
2. Pick your Generic HTTP connection
3. Pick the Send request action
4. Configure the request per-step (these fields live on the macro step, not the connection):
   • Method — GET / POST / PUT / PATCH / DELETE
   • Path — appended to the base URL, e.g. /items or leave blank for the root
   • Headers — JSON object, e.g. {"Content-Type": "application/json", "X-Foo": "{{ctx.session.name}}"}
   • Body — raw string; JSON is recommended. Supports {{ctx.*}} interpolation throughout

#Recipes

#Recipe 1 — Post to a Make.com webhook

Connection base URL: https://hook.make.com/abc123.

#Recipe 2 — PATCH a Linear issue on session end

Connection base URL: https://api.linear.app/graphql, auth: bearer <linear-api-key>.

#Recipe 3 — Call an internal alerting endpoint with a shared secret header

Connection auth: header, secret value: X-Internal-Secret: <your shared secret>.

#Limits and guardrails

#Troubleshooting

#SSRF_BLOCKED validation error

Tevyr blocks requests to private IPs (RFC 1918), localhost, and link-local addresses. Expose the target via a Cloudflare Tunnel, Tailscale Funnel, ngrok, or a public reverse proxy.

#401 with bearer auth set

The token is expired or the header format is wrong. The bearer auth type sends Authorization: Bearer <token> — if your provider uses Authorization: Token <token> instead, switch to header auth and set the secret to Authorization: Token <token> literally.

#Response captured as truncated: true

You hit the 1 MB response cap. Pick a more specific endpoint that returns less data, or use pagination params if the provider supports them.

#Body interpolation comes out as the literal placeholder string

Check the resolved body in the macro fire log (Step inspector → expand the step). If {{ctx.session.name}} came through verbatim, the macro fired without a session context — confirm the trigger is on_session_* rather than a manual fire.

#Context variables

URL, header, and body fields all support {{ctx.*}} interpolation — Tevyr resolves them at fire time. See the full context-variable reference in the Macros guide. Common ones: {{ctx.event.title}}, {{ctx.session.title}}, {{ctx.session.speaker_name}}, {{ctx.timer.remaining_seconds}}, {{ctx.now.iso}}.

#Triggered by webhook events

Generic HTTP can be fired automatically from any webhook event. When creating a webhook, pick Integration mode and select your Generic HTTP connection — Tevyr fills the body with {{ctx.*}} data from the event.

#Related

• Macros — wrap a Generic HTTP call in retry/branch logic via the macro builder
• Integrations overview — see if there's a dedicated template before reaching for this one
• Webhooks — the inverse direction: Tevyr → 3rd-party listeners via Tevyr's built-in webhook engine
• Zapier guide — Zapier-specific shortcuts that build on the generic HTTP pattern