Support

Stuck? Get a human.

No ticket maze and no bot that asks you to rephrase. Email the team directly — and if you send a request ID, we can usually answer in one reply.

MON–FRIFIRST REPLY WITHIN 1 BUSINESS DAYSECURITY 2 BUSINESS DAYS
FASTEST FOR MOST THINGS

Email us

A real person on the product team reads these. Include the details below and you will usually get an answer, not a triage form.

support@stacklink.in
MON–FRI · 10:00–18:00 IST · BUSINESS EMAIL PRIORITIZED · CONTRACT RESPONSE TIMES ONLY WHEN AGREED
BUYING OR SCALING

Talk to sales

Volume pricing, custom quotas, an MSA, security questionnaires, or a provider we don't support yet.

Talk to sales

support@stacklink.in

ENTERPRISE PLANS & DILIGENCE
SOMETHING LOOKS WRONG

Report a vulnerability

Found a security issue? Send it straight here — not to the public channels — and we will take it seriously.

support@stacklink.in
ACK WITHIN 2 BUSINESS DAYS

Tell us this and we can usually fix it in one reply

Most back-and-forth is us asking for the same five things. Save a round trip.

The request ID — every log row has one, like req_x8k2f4. It is the single most useful thing you can send.
Which toolkit and tool — e.g. ZOHO_BOOKS.REMINDER_SEND.
What you expected versus what happened.
When, with a timezone — it narrows the logs fast.
Which client — Claude Code, Cursor, Codex, your own SDK app.
Never send credentials. Not tokens, not API keys. We will never ask for them.
01A tool call failed. Where do I look first?+
Open Logs and find the run. Every call records its arguments, the result and the error, and reading logs is free on every plan. If the provider returned the error, the message is passed through verbatim — that usually tells you whether it is a scope problem, a rate limit, or bad input. Still stuck? Send us the req_ id.
02My user connected an app but the agent says it has no access+
Almost always a scope issue: the consent screen granted less than the tool needs. Check the connection in Auth Configs, then have the user reconnect and accept the full set. Remember grants are per user — one person connecting does not give the whole workspace access.
03A write is stuck waiting for approval+
That is the ask-first gate doing its job. Approve or deny it from the run, and it executes exactly once. If nobody approves, it stays held rather than running quietly — by design.
04I reached an allowance or budget+
The 30-day trial has one fixed allowance and never bills automatically. Paid allowances reset monthly from your billing start date, including on annual plans. Additional operations and managed resources require separate Admin-approved budgets, initially $0. Work that would exceed a limit stops with a clear error; previously incurred charges remain payable. See Pricing.
05You don't support the app I need+
Ask for it. There is a request form on the Toolkits page — give us the app and, if you can, a link to its API docs. Most requests are live within 24 hours.
06I need a DPA, a security questionnaire, or a subprocessor list+
Write to support@stacklink.in. Worth reading Security first — it states plainly which certifications we do and do not hold today.
07How do I delete my data?+
Memory records, subjects, sources, connections and projects have self-service controls. Full workspace erasure requires a verified request to privacy@stacklink.in. Data deletion explains each path.

Before you write, these usually answer it

The documentation covers setup, SDKs and the MCP endpoint; the catalog tells you what a toolkit can actually do.

Documentation — quickstarts, SDK references, the MCP endpoint, and webhook signing.
Toolkit catalog — every tool and trigger, with its typed contract and whether it asks first.
Pricing — tool calls, delivered events, Memory and Workbench usage, and what never counts.
Security — how tokens are stored, and how to report a vulnerability.

Pick a playbook. Keep the guardrails.

Plug in once — MCP or SDK — and every product on this page is already in the run.

30-day trial · no card · first tool call before your coffee cools