Skip to main content
cronable
HubSpot integration

HubSpot automation that keeps your CRM current.

Every lead that arrives somewhere other than HubSpot is a contact somebody has to type in. Cronable creates and updates contacts and deals as things happen, and reacts when HubSpot itself changes, all from a machine you run.

HubSpotHubSpot · ActionHubSpot webhook · Trigger
All integrations
One workflow, end to end

A HubSpot workflow on the canvas

Each card is one job. A wire means the next job runs when the one before it succeeds, or when it fails.

jobs/sales
Or type it to the assistant

“When someone fills in the contact form on my site, create the contact in HubSpot, draft a first-touch email with Claude and send it to me in Slack.”

What you can do

Every HubSpot step Cronable ships

Actions

Steps a workflow can take in HubSpot.
  • Create a contact

    Add a contact with email, first and last name, phone and company, plus any other properties as JSON.

  • Update a contact

    Change properties on a contact found by its ID or by a unique property such as email.

  • Search contacts

    Find contacts by text, choose which properties come back, and page through up to 200 at a time.

  • Create a deal

    Open a deal with a name, amount, stage and pipeline.

  • Custom request

    Reach any other HubSpot CRM endpoint with your own method, path and JSON body.

Triggers

What starts a HubSpot workflow.
  • HubSpot webhook events

    Starts a run when HubSpot sends a webhook batch: a contact, company or deal created, or a property changed. A For each step handles every event in the batch, and each delivery’s signature is checked against your app’s client secret.

Popular workflows

HubSpot workflows worth automating first

01

Speed to lead

Your website form posts to a webhook trigger. HubSpot gets the contact, Claude drafts a personal first email, and the rep sees it in Slack within seconds.

02

Deals from payments

When a Stripe checkout completes, create a HubSpot deal for the amount and update the contact’s lifecycle stage in the same workflow.

03

New-deal alerts

The HubSpot trigger fires when deals are created; a For each step looks up each deal with a custom request and posts its name, amount and stage to #sales.

04

Weekly contact clean-up

Search contacts every Friday, let an AI step spot missing companies and odd-looking records, and post a fix list for someone to review.

How you connect

Connecting HubSpot

HubSpot uses two keys. Both are pasted, and neither needs Cronable to host an app.

  1. 1For actions, create a Private App in HubSpot with the CRM scopes you need and store its access token (pat-…) as a bearer token credential.
  2. 2For the trigger, subscribe to events in your HubSpot developer app’s webhook settings and point them at the job’s hook URL.
  3. 3Add the app’s client secret and the exact notification URL to the trigger, and every batch is signature-verified. Inbound webhooks reach your machine through Cronable’s relay, from the Basic plan up.
Why Cronable

Your HubSpot automation, on your own machine

Runs on your own machine

Install Cronable as a Mac or Windows app, or on a server you own. Your HubSpot jobs, secrets and run history stay on that machine by default.

Built from one sentence

Describe the workflow in plain English and the built-in assistant builds the jobs, the schedule and the failure handling for you to review on the canvas. On every plan, including Free.

Unlimited runs

Plans count the jobs you define, not how often they fire. A job that touches HubSpot every hour costs the same as one that runs once a month.

Credentials encrypted locally

Keys and tokens are AES-256-GCM encrypted in a local database, referenced from jobs by name and masked out of logs and run output.

Questions

HubSpot automation, answered

Can Cronable create HubSpot contacts and deals?

Yes. It creates and updates contacts, searches them, creates deals, and calls any other CRM endpoint with a custom request.

What kind of HubSpot token do I need?

A Private App access token for the actions. HubSpot retired API keys in 2022, and a Private App token is its long-lived server-to-server credential. The webhook trigger verifies deliveries with your developer app’s client secret instead.

Where are the HubSpot keys stored?

Encrypted on your own machine. The access token lives in the credential store, the client secret can be stored as a secret so it never lands in the job file, and both are masked in logs.

Can a HubSpot change trigger a workflow?

Yes. Point your HubSpot app’s webhook subscriptions at the trigger’s hook URL and each batch of contact, company or deal events starts a run. Inbound webhooks are included from the Basic plan.

Does HubSpot send one event at a time?

No, HubSpot batches them. Put a For each step under the trigger and the next job runs once per event, reading its type and object ID.

Anything you do twice in HubSpot is cronable.

Typing leads into HubSpot is not a job for a person. It is a workflow.