Sales automation tools: what to automate, which tool does each job, and where rules stop

Every page on the first results page for "sales automation tools" is written by a company that sells one, and most rank their own product first. This one is written by one too: Tulina runs sales and RevOps processes as AI agents, and its section is below, clearly marked. The rest of the page is sorted by the job a tool takes off a rep, not by brand, because "which tool" only has an answer once "which job" does.

One scope note. Finding who to contact (lead databases, AI prospecting tools) is its own category with its own buyers and is covered elsewhere on this site. This page is about what happens once a lead, a meeting or a deal exists: the work between "someone is interested" and "the CRM says what happened".

What are sales automation tools?

Sales automation tools are software that does a step of the sales process without a rep doing it by hand: assigning a new lead to an owner, sending the next email in a sequence when the last one got no answer, offering the buyer a meeting slot, writing the call's notes into the CRM, creating the deal, reminding the rep of a task. Most of them are features of a tool the team already owns, the CRM's workflows or the sequencer's steps, and the rest are glue that moves a record from one tool to the next.

All of them are rules: when this happens, do that. That is their strength, because a rule does the same thing every time, and their limit, because the sales steps that cost the most time are the ones where the right action depends on reading something first.

What should you automate in sales?

The steps that repeat, that a rep does the same way every time, and that delay the buyer when they wait. In practice, these nine, roughly in the order teams automate them:

Two columns, because almost every row has both. The "rule" column is what every tool on this page sells, and it is worth buying: a lead that waits a day for an owner is a lead that went cold. The "judgment" column is what still lands on a rep after the rule ran, and on most teams it is where the hours go.

What we automate ourselves, counted

Tulina runs its own sales on the same kind of hosted agents it sells, so we counted them. On 29 October 2026 our own workspace had 46 hosted agents switched on, read from the agent list. Twenty-two of them do new-business sales work; the other twenty-four run customer success, support, product, billing, marketing and maintenance jobs.

The split says what we found worth automating first: nearly half the sales agents handle what happens after a buyer answers, not the sending. Every one of the seven reply and follow-up agents drafts or alerts and leaves the send to a person.

Sales automation tools by category, with prices

One or two picks per job, read on each vendor's own pricing page on 29 October 2026. "Quote" means the page prints no number.

HubSpot is the one gap in the table. Its live pricing page did not show tier prices in text when we read it, and a search snippet of the same page showed discounted figures, so no HubSpot price is quoted here. What HubSpot's own knowledge base says is the part that decides it: sequences need Sales Hub Professional or Enterprise. PandaDoc, the usual pick for quotes and proposals, refused our read, so it has no row.

Two things the table hides. Seats and steps are different meters: the CRM and the sequencer charge per person who uses them, the glue tools charge per action or per run, so a busy automation used by one admin can cost more than the CRM seat it serves. And most of the automation a team needs is already in the plan it pays for: before buying a tool for a job, check whether the CRM's own workflows reach it on the current tier. The n8n alternatives page compares the glue tools' units in detail.

What are the top 5 sales automation tools?

The honest top five is one tool per job, and most teams already own three of them: the CRM's own workflows (Salesforce, HubSpot, Pipedrive or Attio) for routing and deal updates; a sequencer (Lemlist, Outreach or Apollo) for the emails that follow up on their own; a scheduler (Calendly, or Chili Piper when routing is the point) for the meeting; a call recorder (Granola or Gong) for the notes; and a glue tool (Zapier, Make or n8n) for whatever crosses between them.

What the five leave undone is the same thing in every stack: the moment between two tools when someone has to read something and decide. That is the next section.

Rules-based vs agentic sales automation

Rules-based automation does what you wired in advance: when a deal moves to "proposal", create a task; when a lead fills the form, assign it by country. Agentic automation reads the record first and decides within rules you wrote: this lead is a fit, so it goes to the account executive; this reply is a referral, so the referred person gets the next message; this call moved the close date, so the deal's date changes and the note says why.

The two are not rivals. The cheapest sales automation is a rule, and every job that can be a rule should stay one. The agent belongs in the step where today a rule hands the record to a person in Slack and waits: that hand-off is the time the team is trying to save.

How do you automate your sales process yourself?

By the hour, not by the tool. This is the order that works whichever tools you use, and it can stop at any step.

1. Time one week of rep work. Ask each rep to note, for a week, what they did that was not talking to a buyer: copying notes, updating stages, writing the same follow-up, chasing a meeting time. The longest line is the first thing to automate.
2. Split each task into moves and decisions. "Create a task when the deal reaches proposal" is a move. "Decide whether this reply is interested" is a decision. Moves go to rules first.
3. Use what the CRM already does. Routing, stage-based tasks and reminders are in most CRMs' own workflows on the tier you pay for. Turn those on before you buy anything.
4. Put every outbound message behind a sequence that stops on reply. The sequencer's job is the second and third email nobody remembers to send, and the stop on reply is what keeps it polite.
5. Make booking one click. A scheduling link in the first reply, and routing by territory or by account owner when several reps share a calendar.
6. Send the call into the CRM. A recorder that writes a summary, and a rule or an agent that attaches it to the right deal with the next step and its date. The follow-up email starts from that record. The sales call follow-up email article has the templates and the timing.
7. Write the rule for each decision in one sentence. "A reply is positive when it asks for a time, a price or a person; an out-of-office is not a reply." That sentence is what a filter, a person or an agent will apply.
8. Keep a person on every message a buyer reads, for two weeks. Drafts, not sends. Read what the automation would have sent, and loosen it only when the drafts stop needing edits.

How do you automate the sales process with Claude or ChatGPT?

With Tulina, Claude or ChatGPT runs a sales job as a hosted agent: on a webhook or a schedule, it reads the systems involved, applies the rules you wrote to each record, does the moves, and leaves the judgment calls it is not allowed to make for a person. Every run shows its steps, its tool calls and their cost. A person still writes the rules, owns the deals, and sends what a buyer will read.

The job below is the inbound one, the oldest in sales automation: a new trial signup arrives, and by the time the person is still in their first session the account is checked, scored, routed to the right rep with a deal open, and the first message is waiting as a draft. Once PostHog, Apollo, LinkedIn, HubSpot, Stripe, Gmail and Slack are connected, paste this into Claude or ChatGPT, or save it as a process that runs on each signup:

A new trial signup just arrived: [name, work email, company]. Turn it
into pipeline without sending anything.

1. Enrich the person and the company with Apollo, and read the
   person's LinkedIn profile: title, seniority, company size,
   industry, funding.
2. Check HubSpot and Stripe for the same company: an existing
   account, an open deal, a paying subscription, an earlier signup.
   A signup from a customer goes to the account's owner, not to
   sales; tell the owner in Slack and stop there.
3. Score the fit against our profile: [one paragraph ICP]. Below the
   bar, the signup stays self-serve: write the plan on the contact
   and stop.
4. Read the person's first session in PostHog: what they connected,
   who they invited, what they created, where they stopped.
5. Choose the play with our activation rules: [sales-assist,
   enterprise hand-off or nurture, and when each applies]. Name the
   rule you used.
6. For sales-assist and enterprise, open a HubSpot deal on the
   company with the owner our routing rules name, and leave a note:
   the signup, the fit and its reason, the first session, the play.
7. Draft the first email in Gmail, in the owner's name: name what
   they did in the session, propose a call. Draft only.
8. Send the owner one Slack message: who signed up, the fit, the
   play, and where the draft is.

The process behind that prompt, with every step and the tools it uses:

The process in Tulina

Turn signups into pipeline

Trigger · Event

New signup

A signup event in the product opens the run, so the first message and the rep's brief are ready while the person is still in their first session.

PostHog

Claude runs the rest autonomously

1. 1

   AI enriches the person and the company.

   Apollo.io

   Apollo.io

   The signup's title, seniority and company size, funding and industry come back from two sources, so a name and a work email are enough to start.

   LinkedIn

   LinkedIn

2. 2

   AI checks the CRM and billing for the account.

   HubSpot

   HubSpot

   Any account, open deal, customer status, paying subscription or earlier signup from the same company comes back, so a signup from a customer goes to its owner and not to sales.

   Stripe

   Stripe

3. 3

   AI scores fit against your ICP.

   The signup is scored on your own profile, and one below the bar goes self-serve with the product's own onboarding and nothing more.

4. 4

   AI reads what they did in the first session.

   PostHog

   PostHog

   The systems they connected, the colleagues they invited, what they created and where they stalled come back with their times, which is what the messages will name.

5. 5

   AI chooses the play from your activation rules.

   Your own rules pick sales-assist, an enterprise hand-off or nurture from the fit and the first session, with the timing of the call, and the rule is named.

6. 6

   AI drafts the first-week messages.

   Gmail

   Gmail

   Three messages are planned for the first week and the first waits as a draft in your voice, naming what they did and proposing the call, never sent.

7. 7

   AI opens the deal, brief the rep.

   HubSpot

   HubSpot

   For sales-assist and enterprise the deal opens for the rep your rules name, with the signup, the fit, the first session and the play, and the rep gets the brief and the draft.

   Slack

   Slack

See the full process

Step 2 is the one a rules-based version gets wrong most often. A form workflow assigns the lead by territory before anything else happens, so a signup from an existing customer lands with a new-business rep. Here the CRM and billing check comes first and costs no enrichment credit if it ends the run.

What running it looks like, measured

The same shape runs on our own replies. Our agent for positive email replies is started by Lemlist when a prospect replies to a campaign: it reads the reply and the lead, and posts an alert with a suggested reply to our sales channel, sending nothing itself. Read from its delivery log on 29 October 2026, it was started by 27 replies that Lemlist delivered between 16 and 28 October (three test calls of our own on 16 October are not counted). Drafting and alerting rather than sending is the point: when a run goes wrong, the cost is a reply a person reads a little later, not a wrong email in a prospect's inbox.

For the follow-up after a call, the job most teams automate next, see Follow through on sales calls.

What sales automation can't do, and what gets you in trouble

• Fix a process nobody wrote down. Automation repeats the process you have. If two reps follow up differently, a sequence picks one of them, and the other rep's buyers get the wrong one.
• Send at volume without consequences. Email providers and LinkedIn limit the sender, not the tool. A sequence that sends from one domain at volume spends that domain's reputation; the LinkedIn automation tools page covers LinkedIn's own rules.
• Keep a sequence polite after a reply. Every sequencer stops on reply, but only on a reply it sees. A buyer who answers from another address, by phone or on LinkedIn keeps getting step three unless something ties those channels back to the record.
• Make a CRM true. A workflow that moves stages on a field change makes the pipeline look current, not be current. A forecast built on automated stage changes is only as good as the rule behind them.
• Decide what a buyer meant. A rule reads fields. The sentence "let's talk after the board meeting" is a date, an owner and a risk, and no field-based workflow sees any of it. That is the step to give to a person or to an agent that sends its unclear cases to one.

Are there free sales automation tools?

Yes, and enough to start. On 29 October 2026 the free plans we read were Salesforce's Free Suite, Attio's free plan for up to three seats, Apollo's free Starter plan, which it says "stays free with no time limit", Calendly's free plan with one event type, Granola's free plan with 30 days of history, Zapier's free plan for 100 tasks a month, Make's free plan with 1,000 credits a month, and n8n's self-hosted Community Edition. Lemlist, Pipedrive and Gumloop offer free trials rather than free plans. The usual limit is not features but volume: a free plan runs one rep's automations, not a team's.

Which CRM has the most automation built in?

On the plans we read, the answer depends on the tier more than the brand. Salesforce lists "Built-in Sales Flows and Lead Routing" from its $25 Starter Suite. Pipedrive's automations start on its $39 plan, not its entry one. HubSpot's knowledge base puts sequences on Sales Hub Professional, and its pricing guide describes Starter's automation as tasks and email notifications when a deal changes stage. Attio puts sequences on its Pro plan. Whichever CRM you have, check the tier you pay for before buying a separate tool for routing or sequences: the automation may already be there, one plan up.

For the wider stack these tools sit in, from data and signals to analytics, see GTM tools, layer by layer.