SEOMURAI Documentation · PRO
Webhook Workflows: Connect SEOMURAI with n8n, Zapier, and Make.
Send page data or DataForSEO results to an external workflow with a single click. Every field is defined as a named JSON key, so n8n, Zapier, and Make nodes can process the data directly. Includes two ready-made starter templates. See the PRO overview or the documentation overview.
PRO feature. 5 USD per month or 50 USD per year via ExtensionPay.
What Webhook Workflows does in SEOMURAI
Many SEO tasks are part of larger processes: an audit finding ends up in a spreadsheet, a SERP evaluation fills a Notion database, a competitor watch triggers a Slack notification. Instead of copying these handoffs manually, SEOMURAI sends the relevant data directly to your workflow.
A workflow defines which fields go where. You choose a webhook endpoint (for example an n8n, Zapier, or Make address), specify for each desired JSON key which SEOMURAI source supplies the data (URL, title, meta description, SERP results, backlink profile, and so on), and give the workflow a name. From that moment on it is available as a one-click action, both in the Webhooks tab and via the right-click menu on any page.
When Webhook Workflows are especially worthwhile
- When you build a permanent content database, for example in Google Sheets, Airtable, or Notion.
- When audit reports should receive new findings automatically as soon as you analyze a page.
- When you monitor competitors and new SERP results or backlink finds should go straight to Slack, Microsoft Teams, or an internal reporting system.
- When you pass content on to other tools (for example WordPress, Webflow, a headless CMS, or a briefing tool).
- When you build your own AI pipeline that needs SEOMURAI data as input.
Step by step
1. Open the Webhooks tab
Switch to AI & Automation → Webhook Workflows. At the top you will see two buttons: “Add Workflow” for your own configuration and “Load Starter Templates” for the ready-made examples. Below them, SEOMURAI lists all workflows you have already saved.
2. Start with a starter template (recommended)
Click “Load Starter Templates” to see the two ready-made examples:
- SEO Audit to Google Sheet: 9 fields per page (URL, title, title length, description, description length, canonical, robots, headings, word count) are written to a Google spreadsheet.
- DataForSEO SERP to Notion: 5 fields from a SERP query (keyword, location, top URLs, top domains, timestamp) are added as a new row to a Notion database.
Each template offers two actions: “Add to My Workflows” clones the template with all its field mappings into your workflow list (you only need to enter the webhook URL), and “Download n8n JSON” downloads a ready-made n8n workflow file from minoka.de that you can import into your own n8n instance. The downloaded n8n file contains sticky notes with step-by-step instructions plus a version marker.
3. Define your own workflow
Via “Add Workflow” you create your own workflow without a template:
- Name: a descriptive label that later appears in the context menu.
- Webhook URL: the endpoint of your n8n, Zapier, or Make workflow.
- Method: usually POST, in rare cases GET.
- Fields: any number of pairs consisting of “your own field name” and “source from SEOMURAI”. The source selection covers page data (URL, title, meta, headings, word count, schema, and more), DataForSEO results, and general values (current time, browser language). Since version 1.7.0 the source selection also includes 14 new webhook sources from the new DataForSEO tabs AI Visibility, Ask the LLMs, and Google Trends.
4. Run the workflow
In the Webhooks tab you run a workflow by clicking the send icon. SEOMURAI sends the assembled JSON structure to the endpoint and displays the HTTP response. Alternatively, you can enable the context menu for each workflow. The entry then appears in the right-click menu on any page, and you can trigger the workflow without going through the SEOMURAI interface.
5. Evaluate responses
On a successful response you see HTTP status 200 plus the workflow’s reply. On errors (4xx, 5xx, or connection failures) SEOMURAI shows a clear message with a diagnostic hint. For workflows triggered via the context menu, the response appears in the Webhooks tab the next time you open the extension, and the SEOMURAI icon shows a small success or error indicator.
Frequently asked questions
Tips and frequently asked questions
Do I need an n8n server?
No, n8n is a recommendation, not a requirement. Webhook Workflows work with any endpoint that accepts HTTP POST or HTTP GET. Zapier, Make, your own cloud function (Vercel, Cloudflare Workers, AWS Lambda), a WordPress plugin with a REST endpoint: all of these work. n8n is popular because it is open source and can be self-hosted.
How does authentication work?
For each workflow you can define additional HTTP headers, for example Authorization: Bearer … or X-API-Key: …. Recommendation for n8n: use the webhook authentication options directly in the webhook node (header auth or basic auth). For Zapier and Make you usually pass a secret path segment as part of the URL.
Which fields can I send to my workflow?
From the SEOMURAI modules: all Tech SEO fields (title, meta description, canonical, robots, lang, viewport, hreflang), content fields (word count, readability, headings list), link fields (internal and external links), schema data, and more. From DataForSEO: SERP results, keyword data, domain evaluations, and backlink profiles from the most recent history entry per module. Plus general values such as current time, URL, and browser language. Since version 1.7.0, 14 new webhook sources from the new DataForSEO tabs AI Visibility, Ask the LLMs, and Google Trends are also available.
Does the context menu stay visible after logout?
No. The webhook context menu is a PRO feature and is removed immediately on logout. The same rule applies to the AI assistants in the context menu. When you sign in again and PRO is active, the entries reappear automatically. This Pro gating logic is defined as strictly enforced in an internal audit (creation with a Pro check, a repeated check on click, and an update on every payment event).
Can several workflows run in parallel?
You can define any number of workflows and trigger them individually. Triggering several workflows at once with a single click is currently not planned, because in practice it creates load on the receiving side that is hard to control. Within an n8n workflow you can of course start any number of follow-up actions after the first request arrives.
More PRO modules and documentation
- PRO overview: all modules, pricing, activation
- Link Heatmap: Visualize link prominence with Fitts’s Law
- Sitemap Explorer: Crawl XML sitemaps and extract URL lists
- SEOMURAI Chatbot: Chat interface with page context
- LLM SEO Team: Specialized AI assistants
- AI Presets: Pre-configured setups for four AI providers
- Markdown Export: Entire pages as AI-optimized Markdown
- Back to the documentation overview (Free)
Unlock Webhook Workflows with PRO?
Install SEOMURAI, activate PRO, and adopt one of the two starter templates as a quick start.