Skip to main content
Use the @bijection/connectors/outreach entrypoint to declare Outreach resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Prospects, accounts, sequences, mailings and calls

The following example matches configuration prospects.

Configuration: prospects

Case: outreach/records/pull/prospects. Connection and resource configuration are declared by this exact case. Credential kind: outreach. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: prospects
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: outreach/records/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: outreach. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: prospects
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds an outreach OAuth bearer for https://api.outreach.io/api/v2/, with one 10,000-an-hour bucket per connection. records.pull reads prospects, accounts, sequences, mailings or calls with filter[updatedAt]=<since>..inf, sort=updatedAt and count=false, following links.next as the host-checked continuation, and carries the latest attributes.updatedAt to the next pass. Deletion is announced only by destroyed webhooks and /events, and a point read’s 404 settles nothing, so nothing is withdrawn. With updates: "webhooks", an Outreach resource webhook asks for a point read of data.id. Outreach signs the body with HMAC-SHA256 (hex in Outreach-Webhook-Signature, sent only when the webhook has a secret: install it as the listener’s signing credential), so a delivery proves a refresh hint. A delivery has no identity: the SHA-256 of its exact body is one. Register the webhook for this resource type only. The organization fields of GET /api/v2 are undocumented, so no account identity is declared, and no write is declared. Nothing here has run against Outreach.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.