Skip to main content
Use the @bijection/connectors/highrise entrypoint to declare Highrise 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.

People

pull: since windows over updated_at, offset pages, no deletions

The following example matches configuration standard.

Configuration: standard

Case: highrise/people/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: highrise. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: people
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Companies

pull: since windows over updated_at, offset pages, no deletions

The following example matches configuration standard.

Configuration: standard

Case: highrise/companies/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: highrise. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: companies
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Deals

pull: since windows over updated_at, offset pages, no deletions

The following example matches configuration standard.

Configuration: standard

Case: highrise/deals/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: highrise. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: deals
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Notes, emails and comments

pull: since windows over the recordings feed, typed rows, no deletions

The following example matches configuration standard.

Configuration: standard

Case: highrise/recordings/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: highrise. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: recordings
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. Highrise stopped taking sign-ups on 2018-08-20; existing accounts keep working. The connection’s setup is the account’s base URL (https://<subdomain>.highrisehq.com/) and the userAgent Highrise asks every integration to send (its name plus a contact). The highrise credential is a basic envelope: the user’s API token (My Info, Integrations) as the user name and X as the password. Reads see what that user sees. Identity is the account’s id from /account.xml. Each collection reads /<type>.xml?since=<yyyymmddhhmmss> (UTC), the rows created or updated since then in ascending updated_at, by offset (n): 500 rows a page for people, companies and deals, 25 for recordings. Each page re-anchors one second before the latest updated_at read; a finished pass carries it and the next starts five minutes before. updated_at is the record version. People, companies and deals keep seven fields, because a 500-row page is one publication; their other scalars are the JSON text details. Contact data, tags and custom fields are not read. People, companies and deals are refreshed by point reads (/<type>/<id>.xml). recordings is Highrise’s /recordings.xml feed: notes, emails and comments in one listing, so they are one collection and type names each row. The reference shows no updated-at in its comment example; a recording without one fails its page. Deletions are not observed: /deletions.xml lists every type in one feed, and a collection must claim every row of a response it reads. A 503 is honoured with its Retry-After; requests share 150 per five seconds (recordings ten per ten seconds). Nothing is written. Nothing here has run against Highrise or been qualified. See the platform’s llm-wiki/wiki/providers/sales-crm.md.

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.