Troubleshooting integrations
Fix connection errors, missing meeting links, silent webhooks and pixels, using the delivery logs and activity views in the app.
Where to look first
Nudge keeps a trace of what it sends to your tools. Start with the view that matches your problem:
| Problem | Where to look |
|---|---|
| A calendar or video tool will not connect | The message shown on the tool page after you come back from the provider. |
| Slots are offered when you are busy, or meetings are missing from your calendar | The tool page: Connected badge and Calendar Settings. |
| A webhook receiver gets nothing | Integrations › Zapier › Delivery logs (eye icon) on the webhook. |
| An ad platform shows no conversions | Integrations › Pixels and tags › Recent activity (pulse icon) on the destination. |
| Slack stays silent | Integrations › Slack: toggle and stored URL. |
Calendar and video connections
Error messages when connecting
| Message | What it means | What to do |
|---|---|---|
| That Google account uses a different address than your AskNudge account. | The account you picked at the provider does not have your Nudge email address. | Connect again and choose the account with the same address. |
| That Google account is already linked to another AskNudge user. | Another Nudge user already connected this account. | Disconnect it from that user, or use a different account. |
| Google could not be linked. Try again. | The provider refused or the round trip was interrupted. | Try again, and approve every step on the provider's page until you are sent back to Nudge. |
| The connection could not start. | Nudge could not open the provider's consent page. | Reload the page and retry. If it persists, contact support. |
| You must be a team member to connect video providers. | Your user is not an active member of this workspace. | Ask an Admin to check your membership in Settings › Team. |
If your company's Microsoft or Google administrator restricts third-party apps, the provider may show a page asking for an administrator's approval. Your administrator must allow Nudge before you can connect.
Slots are offered when you are already busy
Nudge removes from your slots the busy times of the calendar set in Check availability on. If a meeting still gets booked over another event:
- Check the connection. On the tool page, your provider card must show Connected. If Nudge can no longer read your calendar (access revoked or expired), it offers slots from your working hours alone. Disconnect and connect again.
- Check the calendar. The busy event must be in the calendar chosen in Check availability on. If Create events in is a different calendar, a warning reminds you that events in that one do not block your slots.
- Check how the event is marked. Events shown as Free do not block a slot. On Outlook, only Busy and Tentative events do.
Meetings are missing from your calendar
- Check that you have write access to the calendar chosen in Create events in.
- Check whether the form has its own booking calendar in its scheduling settings: it takes priority over yours.
- Check that your Calendar Provider is the provider you actually connected.
A booking has no video link
- The host has not connected the provider selected in the form's Video conferencing setting, or their connection expired. Reconnect on the tool page.
- The provider refused to create the meeting (for example a Microsoft account not allowed to create Teams meetings, or a Zoom account limit). Try another provider or a Custom link.
The calendar list is empty
The list only shows calendars you are subscribed to. If it is empty while you are connected, disconnect and reconnect so the provider asks again for access to your calendar list. You can always enter a calendar ID by hand with Enter a calendar ID….
Webhooks: reading the delivery logs
Click the eye icon on a webhook to open Delivery logs. It shows the last 20 deliveries, newest first, each with the event name, the date and time, and a badge:
| Badge | Meaning | What to do |
|---|---|---|
200–299 | Your endpoint accepted the delivery. | Nothing. If the receiving tool still shows nothing, look at its own logs. |
4xx | Your endpoint refused it (wrong URL, authentication required, payload rejected). | Check the URL. If your endpoint requires authentication, it must accept Nudge's signature instead. |
5xx | Your endpoint crashed or was unavailable. | Fix the endpoint. Failed deliveries are not retried. |
| Error | No answer at all: timeout after 10 seconds, DNS error or connection refused. | Make sure the endpoint answers quickly on a public HTTPS address. |
No deliveries yet means no subscribed event has happened since the webhook was created, the webhook is paused, or the events you ticked are not ones Nudge sends for your use case. Check the event table in Webhooks, Zapier and Make.
If your endpoint rejects the signature, check that it uses the exact secret you entered at creation and computes the HMAC on the raw request body. See Webhooks and event payloads.
Pixels: reading Recent activity
Click the pulse icon on a destination to open Recent activity. Each line is one moment from one source (Browser or Server), with the event name it was sent under, the Total, where the last one came from and when it last fired.
| What you see | Likely cause | What to do |
|---|---|---|
| Nothing received yet. | No visit since the destination was created, the destination is paused, no moment has an event name, or visitors have not given consent on a form that asks for it. | Switch it on, fill in at least one event name, and test with a real visit. |
| No moment reported yet — nothing will fire. on the card | Every event name is empty. | Edit the destination and fill in What to report. |
| Browser far below Server | Ad blockers stop the browser pixel. | Expected. Keep the Conversions API token in place. |
| Only Browser lines | The destination has no Conversions API token (Browser only badge). | Add a token in Edit (Meta). |
| Server lines stop growing while Browser continues | The Conversions API token was revoked or expired. | Run Send a test event; if it fails, generate a new token and paste it in Edit. |
| An error after Send a test event | The message comes from the ad platform. | Usually a wrong pixel ID or an expired token: fix it in Edit. |
For Meta, use a Test event code in Send a test event to see the event arrive live in Events Manager › Test Events without counting in your data.
Slack
- Check that the toggle on the Slack card is on and that the hint says A value is stored.
- If someone archived the channel or removed the webhook in Slack, create a new incoming webhook and paste its URL.
- Slack only receives new bookings, cancellations and, if enabled, handoff briefs. See Slack.
Still stuck?
Write to support@asknudge.ai with the name of the tool, the time of the problem and, for webhooks, the status shown in Delivery logs. Never send your tokens, webhook URLs or signing secrets by email.