July 2026

A HubSpot operation that HubSpot rejected, for a permission you do not have or a record that does not exist, used to come back marked as a success with the real error buried inside the step's output. Those steps now fail, so the run stops at the problem and the error shows on the node. If a HubSpot workflow of yours looked like it was working, check its recent runs.

• HubSpot now asks for the permissions its operations actually need. The core CRM permissions stay required, and everything past them, such as HubDB, files, lists, sequences, marketing campaigns, and custom objects, is requested as optional, so the connection still installs on accounts whose HubSpot plan does not include them. Reconnect your HubSpot credential to grant the new permissions, since an existing connection keeps only what it was granted when you made it.
• HubSpot drops 16 operations that a connected HubSpot account cannot run: the four Webhook Subscription operations, three Calling Extension and two Video Extension operations, the five Social Post operations, List Social Media Channels, and Get Search Settings. The seven HubSpot triggers are unaffected.
• More HubSpot operations now work against a live account. The HubDB row and table operations, blog post and blog author creation, website page creation and updates, and the marketing events, files, audit logs, goals, sequences, business units, and website content listings all return data instead of erroring.

A Slack, HubSpot, or Discord trigger now starts listening as soon as it is part of your workflow, including when the AI builder added it. The subscription used to be created only when you opened the node's config panel, so a workflow you never opened looked ready and quietly missed its events. Existing workflows are repaired on their own within a day. The node's Status field says what it is listening to.

• Ask the AI builder or an agent about one of these triggers and it now tells you registration is automatic and there is no webhook URL to paste, instead of walking you through a manual setup that does not apply.
• A trigger whose Status field showed a registration error now clears it once the trigger is listening again, rather than keeping stale text.