HubSpot connector

The HubSpot connector lets a Neblex workflow or agent treat a HubSpot portal as a source and a destination: read and write records across every object, walk the associations between them, enroll records in workflows and lists, and wake a flow the instant a property changes, without polling the portal on a timer.

• Works against production and HubSpot sandbox portals, switched per connection
• Reads the property and object schema at connection time, so custom properties and custom objects appear with no manual mapping file
• Associations are first class: one step reads a deal's primary company and every associated contact, with no lookup per link
• One connector powers deterministic workflows, agent tool calls, and marketing and sales sync jobs, all in the same run log

The three jobs this connector is picked for most often, and what each one gets you.

• Run a real two-way CRM sync.
• Turn a closed deal into an order.
• Get marketing and sales data to the warehouse.

A real flow revenue teams build early, with the actual field-level detail.

Closed-won HubSpot deal to a NetSuite customer and sales order, associations and all

When a deal reaches Closed Won, Neblex reads its associated company and contacts, creates or updates the customer in the ERP, and raises the order. Deals over a threshold wait for approval first.

1. 1Trigger: Deal stage changed to closedwon, passing the deal ID and amount.
2. 2Read associations: Get associations on the deal returns the primary company and every associated contact with its label.
3. 3Gate: if amount is 25,000 or more, send an approval to the deal owner's manager with the company name and line items. On reject, log a note on the deal and stop.
4. 4Customer: Upsert record on the ERP customer, keyed on external ID hs_company_id, mapping company.name → companyName, company.domain → website, company.country → billing country, and the primary contact's email → email, firstname → first name, lastname → last name.
5. 5Order: create the sales order from the deal's line items, mapping line.hs_product_id → item, line.quantity → quantity, line.price → rate.
6. 6Close the loop: write the order number back to a deal property erp_order_number, and post the order link to the deal owner in Slack.

Common patterns other teams start from with this connector.

• Two-way CRM sync. Contacts, companies, and deals stay in step between HubSpot and Salesforce, with field and owner mapping and conflict rules you control. (RevOps)
• Lead enrichment and routing. New contacts are enriched, scored, deduped against existing records, and assigned an owner before sales ever sees them. (Marketing)
• CRM to warehouse replication. Contact, company, and deal changes land in Snowflake on the next poll, or on the next HubSpot webhook if you point HubSpot's subscriptions at a Neblex endpoint. (Data)
• Inbound triage agent. Given a form submission, an agent researches the company, checks fit against your ICP, and either routes to sales or nurtures, with a note explaining the call. (Agentic)

All standard objects are supported. Custom objects are supported on Marketing Hub and Sales Hub Enterprise. Custom properties are picked up automatically through schema discovery.

Standard objects

Contact, Company, Deal, Ticket, Product, Line Item, Quote, Call, Email, Meeting, Note, Task, Marketing Event, List, Owner

Custom objects on Enterprise tiers, and any custom property, are discovered at connection time and behave identically to standard objects across every operation above, including associations.

The connection is scoped to the OAuth scopes or private app permissions you grant, so it can only touch the objects and actions you approve.

• OAuth 2.0 or private app. OAuth 2.0 for interactive setup, private app tokens for a single portal. Scopes are granted per object and per capability.
• Scope-limited access. A connection with read-only deal scope cannot write deals. Grant the narrowest scope set each flow needs.
• Webhook endpoints. A flow can expose a webhook endpoint for HubSpot to call, protected by an API consumer key with per-consumer rate limits, quotas, and metering.
• Full audit trail. Every read, write, association change, and webhook event flows into the same Neblex audit trail as every other connector.

The shape of the vendor's limits, as published at the time of writing. Verify the exact figures for your plan; they change without notice. Neblex honors the vendor's own rate-limit and retry signals and backs off within them.

• REST calls are limited to roughly 100 requests per 10 seconds per app per portal, with a daily cap that rises by subscription tier and the API add-on
• Batch endpoints process up to 100 records per call
• The Search API returns up to 200 results per page and 10,000 results per query, at about 4 requests per second
• Webhook delivery is at least once, with retries over 24 hours, so a flow must be safe to run twice on the same event
• Rate-limit headers are read on every call, and the connector paces and backs off automatically