Skip to content

septer_query

Read-only access to the Septer system, which manages sales engagement platform (SEP) integrations, outreach cadences/sequences, and SEP job execution.

  • “List the cadences for this tenant.”
  • “Recent SEP jobs for this tenant.”
  • “What’s the bypass-domain config for this tenant?”
ParameterTypeRequiredDescription
tenant_idstringYesTenant identifier — also used as the schema name.
querystringYesPostgreSQL SELECT query.

The search_path is set automatically to "<tenant_id>", "public", so tenant-specific tables (cadences) and public tables (jobs, settings) are both accessible without schema qualification.

Public schema (shared across tenants):

  • jobs — SEP job execution history (job_type, status, input_data JSONB, result_data JSONB, error_message, user_email). Indexed on tenant_id, status.
  • settings — SEP settings (bypass_mailbox_domain, whole_mailbox_bypass, whole_domain_bypass).

Tenant schema:

  • cadences — cached outreach sequences/cadences (outreach_sequence_id, name, enabled, sequence_type, share_type, tags, description, sequence_step_count, owner_email, last_used_at). Unique on (tenant_id, outreach_sequence_id).

List cadences for a tenant:

SELECT name, enabled, sequence_type, sequence_step_count FROM cadences

Recent jobs:

SELECT id, job_type, status, created_at
FROM jobs
WHERE tenant_id = '<tenant_id>'
ORDER BY created_at DESC
LIMIT 10

SEP settings:

SELECT * FROM settings WHERE tenant_id = '<tenant_id>'

JSON with total_count, rows (max 1,000), and truncated.