Integrations · in, out and read-only
Skald integrations: search, leads, alerts and your own tools
Skald integrations bring the search engines' figures and your leads in, send alerts and conversions out, and let a script or an AI assistant read every figure. Read-only where it reads, signed where it sends.
Skald integrations are the roads in and out of Skald beside the server log: Google Search Console and Bing Webmaster Tools, signed webhooks from booking, form and payment tools, alerts and conversions sent to Slack or any address, a read-only JSON API, and an MCP server for AI assistants.
30-day free trial · no card · we set it up within one working day · free to self-host
- hooks The hook receiver answersOK
- tag The script tag sent events todayOK
- calendly Last received 2 h agoOK
- stripe Never received, not even a testNeeds attention
- leads One lead sent by two toolsNeeds attention
- typeform No secret yetOff
Sample status. Each road says what works, what is missing, and the fix.
[01] five jobs
Skald integrations by the job they do
The server log is Skald's main road: it sees people, AI and bots. Integrations add what a log cannot hold, and send out what you want to act on. Pick a job. Everything starts from your server log.
pick a job
What people searched, from the engines themselves
Your log never sees a search: no query, no impression, no position. Skald syncs them from Google Search Console and Bing Webmaster Tools every 6 hours, and shows them on Traffic › Search beside the visits Skald counted itself. They stay the engines' figures, never added to Skald's.
Search Console · 28 days · clicks 1,597 · impressions 70,211 → synced, never forced to match
Every booking, form and payment, signed
Calendly, Cal.com, HubSpot, Typeform and Stripe send a signed webhook. Zapier, Make, n8n and form plugins post the same lead with a plain key. WordPress has a plugin, and your own backend one file. Each lead is kept once, and joined to the visit when the script tag carried the visitor ID.
invitee.created · product-demo → kept · Demos, completed
Tell Slack, your CRM or any tool
Add an HTTPS address, tick the events, and Skald sends each one signed: a conversion by stage, a lead won or lost, an AI reading change, or any alert when it opens. A Slack address gets Slack's own shape. Nothing leaves until an admin adds a webhook, and no message holds a name or an email.
alert.opened · [example.com] 14 server errors in 10 minutes → #site-alerts
Every figure, read-only, by token
A script or a spreadsheet reads the same JSON files the dashboard reads, with a token. An AI assistant asks in plain words through the MCP server and gets the same figures, with the same rules: withheld days named, a figure not recorded is null, never 0.
GET /traffic-api/v1/example.com/overview → 200 · read-only
Count your platform right
A Next.js site opens pages without an HTML request, so one log field lets Skald count each click inside the site and never a prefetch. A WordPress site sends its log, takes the tag in its theme, and its forms become leads through one plugin.
"GET /pricing?_rsc=1x7a" rsc_prefetch=- → a page view
[02] lead sources
Lead integrations: bookings, forms and payments
Each tool has its own address and its own secret in Skald, a test button, and a log of its last 50 deliveries with the outcome in words. One page per tool says what it sends and what Skald keeps.
[03] read-only, opt-in, signed
What leaves Skald, and what never does
An integration is a door. Skald keeps each one narrow, and you can close it at once.
Reading is read-only
The API and the MCP server cannot change a setting, delete data or add anything. A token reads only the sites it was made for, and no visitor addresses unless an admin ticked that.
Sending is opt-in
Nothing goes out until an admin adds an outgoing webhook. Each message is signed, and holds figures and an anonymous journey, never a name or an email.
Secrets shown once
A token or a hook secret is shown when it is made, then never again. Revoke or rotate it, and the old one stops at once. A token also stops when the admin who made it leaves the team.
[04] what it does not do
The limits of Skald integrations, said plainly
What each integration cannot do is on its own page. These hold for all of them.
What it does not do
- Search figures are the engines' own. Skald shows them beside its visits and never forces the two to match.
- The API and MCP only read. Nothing can be written through them, not even a lead.
- The set-up pages need team accounts. On a server with one shared login, whoever runs it sets hooks up there, and MCP is not available.
- The same lead sent by two tools counts twice. The Status list names it; send each lead one way only.
- Integrations add to the log; they do not replace it. Without a server or CDN log, AI crawlers and bots are not seen at all.
in this section
Every integration, one page each
keep reading
More on Skald integrations
questions
Skald integrations FAQ
Straight answers, including what Skald does not do.
Which tools does Skald integrate with?
Google Search Console and Bing Webmaster Tools for search figures. Calendly, Cal.com, HubSpot, Typeform, Stripe, Zapier, Make, n8n, WordPress forms and your own backend for leads. Slack or any HTTPS address for alerts and conversions. A read-only JSON API and an MCP server for scripts and AI assistants.
Do integrations need the script tag?
No. Search Console and Bing are synced server to server. The lead webhooks reach Skald on every install, with or without the tracking script. The script tag adds the visitor ID that joins a booking or a form to the pages read before it.
Can an integration change my figures?
No. The API and the MCP server only read. The search engines' figures are shown beside Skald's own and never added to them. A lead webhook adds a lead; it never changes a visit count.
Who can set up integrations?
An owner or admin of the site's organisation, on Settings › Integrations and Settings › Connections. These pages need team accounts. On a server with one shared login, whoever runs the server sets them up there.
Does anything leave Skald without my say?
No. Sending is opt-in: nothing goes out until an admin adds an outgoing webhook, and an outgoing message never holds a name or an email. The API and MCP answer only a token an admin made, for the sites it was made for.
Is a webhook secret or a token ever shown again?
No. Each is shown once when it is made. Skald keeps only a fingerprint of a token. If one is lost or leaks, revoke or rotate it and make a new one: the old one stops at once.
$ tail -f access.log | skald
See what AI does with your site. Free for 30 days.
No card. We set up hosted Skald for you within one working day, or you self-host it free. Every line of your log, sorted and added up.