Reference

The details behind the HubSpot integration, collected for looking up rather than reading through.

Schedules

Frequency	When it runs
Manual only	Never on its own; only when someone chooses Run now
Hourly	Once every hour
Daily	Once every 24 hours
Weekly	Once every 7 days

A schedule only applies to an active sync. Drafts, paused syncs and syncs in error never run automatically, whatever frequency they carry. One run happens at a time per sync, so a scheduled run is skipped if the previous one is still going.

Statuses

A sync is a draft when first created and runs nothing; active once it is on its schedule; paused when someone stops it; and in error when it can no longer reach HubSpot, usually because the connection was removed or its access revoked. A sync in error carries the reason and does not run again until the connection is fixed and the sync reactivated.

A run is running, completed, or failed. Failed means the run itself could not proceed — HubSpot unreachable, the connection unusable — rather than individual objects failing. Each run reports what it did: pulled, unchanged, created, updated, waiting for review, failed.

An object within a run:

Status	Meaning
Pulled	Read from HubSpot, queued to be written
Pending review	Waiting for approval, on syncs that require it
Approved	Approved and being written
Synced	Written onto an entity record
Skipped	Unchanged since last time, or recognized as Auron's own write coming back
Rejected	Discarded by a reviewer and never written
Failed	Could not be written; the reason is shown against the object

A failed object does not fail its run — the rest of the objects carry on. Failures are retried on later runs up to three times, and an object modified in HubSpot gets a fresh set of attempts.

What is synced

Object type	HubSpot properties
Companies	Any property on the object, standard or custom
Deals	Any property on the object, standard or custom
Contacts	Any property on the object, standard or custom

Only mapped properties are read, and only mapped columns are written. Columns your team maintains in Auron are never touched by a sync.

Values are converted to the entity column's type. Text, email and URL columns take the value as-is; a number column requires a numeric value; a select column requires one of its allowed options. A value that cannot be converted fails that object with an explanation rather than writing something wrong. Properties HubSpot calculates itself — object id, creation and modification dates — are never written back.

Limits

Limit	Value
Objects per scheduled or manual run	500
Objects per sample run	10
Retries for a failed object	3
Objects per outbound push	1 (the record the automation is running on)

A portal holding more than 500 objects of a type is not a problem: the first run takes 500 and later runs continue through the rest until the initial load is complete.

Who can do what

Action	Owner	Admin	Member	Guest
Connect or disconnect HubSpot	Yes	Yes	No	No
Create, edit, delete or run a sync	Yes	Yes	No	No
View syncs and their runs	Yes	Yes	Yes	No
Review and approve pulled objects	Yes	Yes	Yes	No

Reviewing is open to members, since checking whether a CRM value belongs on a record is more about knowing the account than about holding a role.

Approving a push to HubSpot works differently: only the members named as approvers on that automation step can respond to its card, whatever their role. See Roles and permissions.

Cost

Syncing costs no credits. The mapping is a direct property-to-column copy with no model involved, so runs are free however often they happen and however large the portal.

Pushing costs no credits either. Steps earlier in the same automation may — summarizing a meeting, running an agent — but the write itself does not. See Usage and plan.

Notifications

A completed run posts a summary to the organization feed: what it created, updated, parked for review and failed. Runs that produce nothing post nothing, so a quiet portal stays quiet. Objects waiting for review, and objects that failed, also notify on mobile.

Approval cards for outbound pushes appear in the feed of each nominated approver and as a push notification.