Tenka map

Each card is an external integration available to the account: ERP connector, webhooks, API, MCP, WhatsApp, email with your domain, corporate login, OAuth applications and NFS-e. The badge states the REAL status, measured in the database: active, with alert or not configured.

The hub for the account's external integrations: ERP connector, webhooks, public API, MCP, WhatsApp, own SMTP, SSO/SAML, OAuth and NFS-e — each with a measured status (configured, with alert, not configured) and the shortcut to the screen where it's configured. — this is the role of the "Integrations" screen within the platform.

Click Configure on the card — the button takes you to the integration's own screen (the same as always; this screen is the index, not the replacement). Whoever can see this hub is whoever administers the account.

Turn on opens the minimal dialog of the chosen system's recipe: only what it requires (URL, user, token). What you type goes encrypted to the connector; the recipe never stores credentials. A recipe marked "queued" shows what it asks for but does not turn on yet. Test checks the connection right away with the same test as the source screen; an integration without a test says where to check. Configure remains the advanced mode.

In Integrations, the Test button now also checks the service invoice and email from your domain. For service invoices, the stored token is checked at PlugNotas and the message shows the environment. For your own email, a test message goes to your login email; if it arrives, sending from your domain works. If nothing is connected, the message says so.

Active = there's a live configuration. With alert = the last run failed or a channel reports itself as down. Not configured = nothing registered yet. Not measured = the measurement failed — which does NOT mean unconfigured; if it persists, tell support.

Being configured and being WORKING are different things — and the card shows both. The badge states the configuration status; the "last event" line says how many days ago the integration really gave a sign of life. An active integration that hasn't logged an event in weeks deserves the same attention as one with an alert: either the flow dried up, or something stopped calling. The summary at the top counts the configured ones, those with alerts and the total available; each card's Configure button takes you to the exact screen where that integration is adjusted.

The EDI channel has not collected for more than 30 minutes. The EDI with the retailer screen shows the reason for the last cycle. While the real SFTP connection is not available on the server, the real VAN says "SFTP transport not installed"; use the simulated VAN to rehearse.

They live in the Trust Center ▸ External doors: there you can copy the full link of whatever is shareable, turn each door on and off and see usage over 30 days. Approval, quote and report links are born in the record itself, with a token and a deadline.

Store PIX: check in Settings > Integrations whether the company's Asaas webhook is on with the right token, and look at the charge in the Asaas portal; when the payment notice comes back, the charge becomes paid and the alert goes away. Card machine: check each approval in the Stone or PagBank portal and mark it as checked at the register, with authority. The alert limits are in Settings, PDV group (PIX hours and card machine days). The sale never locks because of this alert.