Agent skill · WebAskio
webask-integration-triage
Finds why responses to a WebAsk survey do not reach an external system, and fixes it. Use when someone reports that leads are not arriving in their CRM, notifications are missing in Telegram or MAX, rows are not added to a Google Sheet, or a webhook does not fire.
What it needs
About 2k tokens when loaded.
What this skill does
Why responses are not leaving the survey A silent integration has four different causes, each with a different fix. Work strictly in order: every next step costs more than the previous one. Reply to the person in the language they write in. 1. Get the survey id Nothing can be done without it. If the survey was named in words, find it with getquizlist and confirm it is the right one before changing anything. 2. Read the state: getquizintegrations Returns every integration with a ready-made reason. This covers most requests and costs nothing. Reason Meaning What to do --- --- --- blockedbytariff not included in the plan state it plainly and stop, see the prohibition below notconnected no connection at all connecting happens in the web app: give the steps, do not attempt it disabled connected, sending switched off ask whether that was deliberate; enable only with consent empty settings are fine go to step 3 Webhooks are not in this response — they have their own setup, see step 5. 3. Find the refusal Behaviour differs by system, because not everything has a log. Telegram and MAX — getintegrationlogs. The messenger's refusal text is there: bot removed from the group, chat deleted, topic closed, token revoked. The unsent counter shows how much is waiting. Bitrix24 — no log of its own; use managequizcrm with the check action. It reaches the portal and reports whether access is alive. Tokens are revoked on the CRM side, and from the survey this looks exactly like a working integration — so this step is mandatory even if step 2 was clean. Google Sheets — managequizgooglesheets with the show action. The usual cause of silence is revoked access to the Google account. 4. Resend only after the cause is fixed resendintegrationlogs for messengers: one entry, or all failures in a period. Resending while the cause is alive is pointless — the same refusal repeats and the log fills with noise. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills WebAskio/webask-integration-triage