Use this file to discover all available pages before exploring further.
Webhooks let you react to every new Jam. The workflow recipes below are common patterns, each with steps for one or more no-code platforms, along with a code variant.Every workflow recipe assumes you already have a jam.created webhook endpoint. If you don’t, see Get Started with Webhooks first.
Open a PR from a Jam
Hand a new Jam to an agent that reads the bug and opens a fix PR.
Notify Slack on incoming Jams
Post a Slack message whenever a customer captures a Jam.
Auto-file a Linear or Jira ticket
Forward every new Jam to your tracker as a structured triage issue.
Prioritize Jams from key accounts
Filter by author domain and route high-value reports straight to the team.
Hand a new Jam to a coding agent that pulls the full context through Jam MCP, writes a fix, and opens a PR for review. Best for code-addressable bugs from a small set of senders (yourself, your QA team, a beta user).
This workflow runs an LLM agent against your repository. Scope it to a sandbox repo or a narrow set of paths before any merges land near production.
The flow:
jam.created fires.
A GitHub Actions workflow (or any runner you control) runs with the Jam ID.
The runner invokes an agent that calls Jam MCP for the recording, logs, network requests, and transcript.
The agent writes a patch in a new branch and opens a PR that links back to the Jam.
GitHub Actions
n8n with an agent
1
Add a repository_dispatch workflow
Create .github/workflows/jam-to-pr.yml and trigger on repository_dispatch with event type jam-created.
2
Deploy a small webhook receiver
Stand up a function (Netlify, Vercel, Workers) that verifies the Jam signature and POSTs to GitHub’s repository_dispatch API with the Jam ID in the client payload.
This workflow posts a Slack message whenever a Jam is captured through a Recording Link. Pair it with a public-facing Recording Link to collect feedback from your website and ping the team on every new report.
Every jam.created event becomes a triage issue with the title, description, captured URL, and a link back to the Jam.
Zapier
n8n
Make
Code
1
Trigger on jam.created
Use Webhooks by Zapier → Catch Hook, copy the generated URL, and register it in Settings → Webhooks with the jam.created event.
2
Send an example event from Jam
Open the endpoint in Jam and click Send Example so Zapier picks up the payload shape.
3
Add the Linear or Jira action
For Linear, choose Create Issue. For Jira, choose Create Issue.
4
Map the fields
Title: title (fall back to Bug from <author.email> if empty)
Description: combine description, originalUrl, and jamUrl so the Jam is the first link in the ticket
Status: Triage
Team or Project: pick the triage destination
Labels: tag with the Jam origin
5
Publish the Zap
Run a test and turn on the Zap.
1
Add a Webhook trigger node
Copy the production URL and register it in Jam with jam.created.
2
Add the tracker node
Use Linear → Create Issue or Jira → Create Issue. Authenticate with an API key.
3
Map the fields
Title: ={{$json.body.title || "Bug from " + $json.body.author.email}}
Description: include {{$json.body.description}}, the Jam link {{$json.body.jamUrl}}, and the captured URL {{$json.body.originalUrl}}
Labels: add the value of {{$json.body.origin}}
4
Activate the workflow
Send another example from Jam to confirm the ticket lands.
1
Add a Custom webhook trigger
Copy the URL, register it in Jam with jam.created, and send an example event so Make learns the schema.
2
Add the Linear or Jira module
Pick Create an Issue. Authenticate with your tracker credentials.
3
Map the fields
Use the Jam payload for Title, Description, and Labels. Put the Jam URL on the first line of the description so reviewers click into the recording immediately.
4
Turn on the scenario
Verify with one example event, then enable the scheduler.
The example below files a Linear issue. Swap the API call for Jira’s REST endpoint if you use Jira.
Route Jams captured on key-accountcaptured on key-account domains straight to the team and tag them with a priority label. Pair it with a Recording Link in your help center or status page so a VIP customer’s report never sits in a queue.
The flow:
jam.created fires.
Match the originalUrl host against a list of key-account domains, or look itMatch the originalUrl host against a list of key-account domains, or look it up in your CRM.
If matched, post to a high-priority Slack channel and create a P0 ticket.
If not, fall through to your normal triage flow.
Zapier
n8n
Code
1
Trigger on jam.created
Use Webhooks by Zapier → Catch Hook and register the URL in Jam.
2
Add a Paths step
Zapier’s Paths branches on a condition. Create a path called Key account.
3
Filter the Key account path
Add a Filter: Original URLContainsacme.comORbigco.com. Add one row per domain, or look the host upURL Containsacme.comORbigco.com. Add one row per domain, or look the host up via Zapier CRM integrations.
4
Post to a priority Slack channel
In the Key account path, add Slack → Send Channel Message to #vip-bugs. Include the customer email, Jam title, and Jam URL.
5
Create a P0 ticket
Add Linear → Create Issue (or Jira). Set Priority to Urgent and add a P0 label.
6
Add the fallback path
In the default path, file the Jam in your normal triage queue.
7
Publish the Zap
Test each path with an example event from Jam, then publish.
If you maintain key accounts in HubSpot or Salesforce, swap the static domain list for a CRM lookup step before the Filter.
1
Trigger on jam.created
Add a Webhook trigger and register the URL in Jam.
2
Branch on the capture URLcapture URL
Add an IF node. Condition: {{$json.body.originalUrl}} contains originalUrl}} contains acme.com. Use an OR group for additional domains.
3
Wire the true branch to Slack and Linear
Add Slack → Post a message to #vip-bugs and Linear → Create Issue with priority Urgent.
4
Wire the false branch to your default triage
Send the payload to your existing flow or leave it to a second webhook listener.
5
Activate the workflow
Send a few example events from Jam with different capture URLcapture URLs to confirm routing.