API | Syncs | Request limit | Interval |
---|---|---|---|
Standard | Owners, Pipelines, Associations | 100 | 10 seconds |
Search | Objects (e.g. Company, Contact, custom objects) | 4 | 1 second |
associations_company_contact
with the following structure:additional-fields
Column name | Postgres type | Example value | Description |
---|---|---|---|
company_id | text | ”9457785876” | The associated company’s HubSpot ID. |
contact_id | text | ”36701” | The associated contact’s HubSpot ID. |
labels | text[] | The association’s labels. |
associations_company_contact
, there won’t be a table with the opposite order (associations_contact_company
). These table names are a fixed function of the type names.
You can JOIN
using the associations tables:
associations_car_request
table with the columns car_id
and request_id
.
insert
insert
command. Here’s how to insert a HubSpot contact
:
update
update
command. Here’s how to update a HubSpot contact
:
delete
delete
command. Here’s how to delete a HubSpot contact
:
_sync_hash
, _sync_inserted_at
, and _sync_updated_at
. Don’t be alarmed: Sequin uses these columns to keep data flowing into Postgres smoothly. Just don’t tamper with this data