ALG · Integration Panel

Home

The API call limit is per Salesforce organization and is shared with every application connected to it. This counter only measures what leaves this server.

Recent requests

Every call that reached the server, and which credential made it.

Credentials

Every person or system that queries has their own. They're issued and revoked here — never edited, never shown again.

The Secret column only shows the last four characters. The full value appears once, at creation: in the database it lives hashed and there is no way to recover it. Revoking doesn't delete the row either — the usage history stays queryable.

MCP connector

What you hand over so someone can connect Claude Desktop, VSCode or Cursor. Four values, pasted once.

Add custom connector — exact fields

The Salesforce consumer key does not go here. Only Salesforce understands that credential, and it lives exclusively in the server's environment variables.

MCP credentials

Only the ones a person can paste into an AI client. REST keys live on the next screen.

Tools these credentials can use

Each one is something the person can ask for.

Not built yet. These are the tools planned for Etapa 3. Per-credential switches arrive with them — today a credential can reach everything it is issued for.

API keys

For scripts, dashboards and automations. The key travels in the request header, never in the URL.

The Secret key column shows only the last four characters. The full value appears once, at creation — after that it lives hashed and cannot be recovered.

Endpoints

What a key can reach on this deployment.

Filters on /v1/contacts

Any parameter not on this list returns 400. It is never silently ignored.

Deployment settings

Read from the server's environment. Changing them means changing the deployment, not this page.

Usage

Who queried what, and when. Salesforce only sees one integration user — the per-person trail lives here.

By credential

Recent requests

Historical capture

A daily snapshot of the pipeline fields, stored in our own database.

Not built yet — Etapa 8. Appointment and hire date fields get overwritten in Salesforce, and ContactHistory only tracks from Oct 7, 2025 and retains 18–24 months. A daily snapshot would preserve the history Salesforce is going to lose. Nothing is being captured today.

Users

People who can sign in to this panel and issue credentials. They are not API consumers.

Passwords are handled by Supabase Auth and never reach this server. An administrator issues and revokes; a read only user can look without touching.

Panel activity

Salesforce cannot answer this: to it, everything arrives from the same integration user.

Salesforce

Read-only. These credentials live on the server and cannot be viewed or changed from here.

The consumer key and secret are not shown here, to anyone. They live only in the server's environment variables — so a bug in this panel cannot leak them.

Org API quota

Read from the last real response Salesforce sent. Shared with every application connected to the org.

Fields with caveats

These notes travel inside every API response, not just this panel. The model receives them alongside the data.