septer_query
Read-only access to the Septer system, which manages sales engagement platform (SEP) integrations, outreach cadences/sequences, and SEP job execution.
When to use it
Section titled “When to use it”- “List the cadences for this tenant.”
- “Recent SEP jobs for this tenant.”
- “What’s the bypass-domain config for this tenant?”
Inputs
Section titled “Inputs”| Parameter | Type | Required | Description |
|---|---|---|---|
tenant_id | string | Yes | Tenant identifier — also used as the schema name. |
query | string | Yes | PostgreSQL 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.
Tables
Section titled “Tables”Public schema (shared across tenants):
jobs— SEP job execution history (job_type,status,input_dataJSONB,result_dataJSONB,error_message,user_email). Indexed ontenant_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).
Example queries
Section titled “Example queries”List cadences for a tenant:
SELECT name, enabled, sequence_type, sequence_step_count FROM cadencesRecent jobs:
SELECT id, job_type, status, created_atFROM jobsWHERE tenant_id = '<tenant_id>'ORDER BY created_at DESCLIMIT 10SEP settings:
SELECT * FROM settings WHERE tenant_id = '<tenant_id>'Returns
Section titled “Returns”JSON with total_count, rows (max 1,000), and truncated.