Webhooks (outbound integrations)
Notify YOUR systems when something happens here: invoice paid, proposal accepted, deal won, request created, and lead created — delivered via signed HTTP.
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Send test event
The list shows
EventStatusAttemptWhen
Form fields
DescriçãoPara você reconhecer a integração (ex.: ERP do cliente).
URL de destino*Endpoint HTTPS que receberá o POST com o corpo em JSON.
Ativo
Start here
What it's for
Real-time integration without polling: register a URL of yours and choose the events. When the event happens, we send a POST with the JSON of what occurred.
Webhooks in a list, deliveries at the top
The list shows each webhook with description, URL, events, masked secret and whether it is active. At the top are the latest deliveries — event, status, HTTP code, attempt and when — and the Send test button, which queues a ping to all active subscriptions.
Rules
Security (HMAC signature)
Each subscription has a secret (whsec_...). Every delivery goes with the X-Tenka-Signature header (HMAC-SHA256 of the body) — validate it on your server before trusting the content.
Delivery and retry
Did it fail (timeout/5xx)? The queue resends with progressive backoff. The latest deliveries show up on the screen with status — use the Test button to validate your URL.
Available events
fatura.paga, proposta.aceita, negocio.ganho, demanda.criada and lead.criado. The catalog shows only what actually fires — no empty promises.
Secret and events on the record
On the record, the secret signs the body of each delivery (X-Tenka-Signature header, HMAC): validate it on your side to guarantee the origin. If blank, Tenka generates one; the button next to it generates another. Under Events, keep "All" or choose which events fire — at least one.
Delete removes the subscription
Webhooks do not go to the trash: deleting removes the subscription, and your system stops receiving events right away. To pause without losing the setup, untick Active.
Frequently asked questions
Best practices
Respond with 2xx quickly (process it asynchronously on your side); handle duplicates by the event id (deliveries can repeat on retry).
Was this article helpful?
In the same module: Platform and security38
Connected help screenAnchor screen of the detail dictionary. Does not appear in the menu.Platform accessThe record of when the platform's support team accessed your account, what they did and with what authorizati…White-spaceSee what's left to sell to those who are already customers — by cross-referencing the installed base with wha…Template itemAnchor screen of the detail dictionary (template items). Does not appear in the menu.Assistente fiscalQuatro passos para a nota sair do Tenka: estado, regime, código de segurança (CSC) e certificado A1 — com a r…ShippingControls the picking and dispatch of what was sold. Shipping confirms that the merchandise actually left: a m…Position bandAnchor screen of the detail dictionary (position bands). Does not appear in the menu.Blog — WordPress connectionWhere you connect your company's WordPress and teach the AI to write like you: the editorial line (what to ta…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.