Skip to main content
Configview reads your Salesforge account (AI cold-email outreach) through the Salesforge public API (https://api.salesforge.ai/public/v2), using an API key created in Salesforge. Configview only sends GET requests. It never creates, changes or removes anything in Salesforge. You will end up with 1 required secret (SALESFORGE_API_KEY) in Configview when setup is complete.
Scope of this integration today. Configview answers “which company mailboxes and domains send cold email, which of them lost access or were suspended, which sequences have no mailbox or bounce a lot, where do webhooks deliver, and how many credits have we used”: workspaces, connected sender mailboxes (address, domain, provider, status, daily limit), sequence names with status and counts, webhook names, event types and destination host, credit balances and the subscription plan. It does not read contacts, email or step content, replies, threads, do-not-contact lists, knowledge files or anything from Leadsforge.
Narrow by design. The Salesforge API has no endpoint for team members, roles, invitations, API keys or an audit log, so Configview cannot show who has access to Salesforge or what they did. Warm-up health belongs to Warmforge, a separate product with its own API key, which this integration does not read.
Plan requirement. API access is available on the Growth plan and above.

What you need

  • A Salesforge account on the Growth plan or above, and permission to create an API key
  • Nothing else: there is no read-only role for API keys in Salesforge, so use a key created only for Configview

Step 1: Open the Salesforge page in Configview

Open Configview in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/salesforge

Step 2: Create the API key

  1. In Salesforge open Settings and then API & MCP, and create a new API key. Salesforge’s guide: https://help.salesforge.ai/en/articles/10333607-salesforge-api
  2. Name it, for example, Configview (read-only use)
  3. Copy the key now
  4. In the Configview tab paste it into SALESFORGE_API_KEY under Credentials and save
The key is sent as-is in the Authorization header (no Bearer prefix). No expiry is documented for Salesforge keys and nothing rotates; deleting the key in Salesforge stops Configview.

Step 3: Connect and verify

  1. Click Connect. Configview creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secret and calls GET /me.
If a check fails:
  • 401. The key is wrong, was deleted, or was sent with a Bearer prefix.
  • 403. The plan does not include API access.

Data Tables

Snapshot tables have a run_at column and keep only the newest run.

Things worth knowing

First run: field names are unverified. Salesforge’s published reference describes the items of the workspace, mailbox, sequence and webhook list endpoints with the do-not-contact schema (a copy-paste error), so the real list fields are not documented. Configview reads each field under several likely names (taken from the single-object endpoints). After the first run, check the tables for columns that came back empty (address, status, mailbox_count, url_host) and tell Configview support if any are. Mailboxes. Statuses are active, frozen, access_lost, deleted, inactive, pending and suspended. A mailbox in access_lost has been disconnected from Gmail or Outlook and its sequences stop sending. Signatures and sender names are not stored. Sequences. Mailboxes and steps are only counted. Email subjects and content are never read. Webhooks. Only the destination host is stored; the full URL can contain a token. Each webhook fires on one event type. The signing secret is never read. Rate limit. Salesforge documents no rate limit for the public API (one help article says none is enforced). Configview paces itself at 2 requests per second, waits when Salesforge answers 429, and uses one request per page of 50 rows, per workspace.

Known gaps

  • No team members, roles, invitations, seats, SSO or audit log: Salesforge’s API does not offer them
  • No API key or integration listing
  • Mailbox warm-up health is in Warmforge (separate key), not read here
  • Multichannel (LinkedIn) accounts are not read

What isn’t collected

  • Contacts, leads, do-not-contact lists, tags and custom variables
  • Email and sequence step content, subjects, replies, threads and attachments
  • Knowledge files, products and sender profiles
  • Mailbox signatures and sender names
  • Webhook URLs beyond the host, signing secrets and the API key
  • Anything from Leadsforge (enrichment and search spend credits and return purchased contact data)