The HubSpot WordPress plugin already syncs WordPress forms into HubSpot and exposes the matched contact when the tracking cookie or a logged-in user identifies them. SleekAI reads that matched contact through a small bridge that pulls the properties you want into the system message at request time. If you prefer a direct API call, SleekAI's data-source wizard can also call HubSpot's CRM API with your private app token.

Indirectly. SleekAI describes the action and fires a webhook into a HubSpot workflow or an Operations Hub custom action, which does the actual write. That keeps HubSpot the system of record for properties, deal stages, and lifecycle moves. Letting the bot write directly would bypass your workflow rules, which is why SleekAI guides and HubSpot executes.

Yes. The wizard picks specific properties: first name, lifecycle stage, owner, last submission, and any custom property like industry or seat count. Sensitive internal notes stay out of the prompt by default. Only the contact's own data enters their bot context, so a logged-in contact cannot read another contact's record.

HubSpot's company object groups contacts. SleekAI can read company-level properties alongside contact data, so the bot can reference the account's plan, last renewal date, or designated sales engineer when a contact from that company is identified. Useful for multi-stakeholder deals where the second contact on an account asks a question the first contact's owner already answered.

Yes for read context. SleekAI can pull marketing engagement scores, sales deal stages, and service ticket history into the prompt if those properties are accessible to the API token you provide. Practical limits are about what is appropriate to expose in a chat reply, not what HubSpot stores, so most teams expose a curated subset of fields.

Inside WordPress, with model name, token usage, page URL, and the matched HubSpot contact ID stored per session. You can hand-off a full chat log to a HubSpot timeline event via a workflow webhook so reps see the conversation in the contact record without leaving the CRM. The WordPress log stays the durable copy.

Yes. Treat HubSpot consent and subscription type the same way you would for any CRM read. Filter the contact lookup by consent or subscription status, and the bot will only personalize for contacts who agreed to marketing or sales communication. Anyone who unsubscribed or never consented falls back to the stranger bot with no personal context exposed.

Yes if your token has access to them. SleekAI's wizard treats HubSpot custom objects like any other data source, so a B2B SaaS using a Subscription custom object can include the current contact's active subscription, MRR, and renewal date in the bot's prompt. That keeps the bot's pricing answers in sync with actual contract terms.