How to Automate Lead Follow-Up in Pipedrive

Start with Pipedrive's built-in tools when a fixed email and a follow-up activity cover the job. Use a connected system when the message needs outside context or an approval queue across tools. I'd settle the lead follow-up strategy first: what deserves an email, what deserves a call and when to stop.

What Can Pipedrive Automate Natively, and Which Plan Do You Need?

Automations combine a trigger with actions such as updating records, creating activities and sending email from a synced account. Correct permissions are required to create automations.

As at 10 October 2026, the current plans are Lite, Growth, Premium and Ultimate. Older help pages use Advanced for Growth and Professional for Premium; Pipedrive explains the plan changes.

Sources: Automations availability, Sequences availability and company limits. For subscription budgeting, read my Pipedrive cost guide for Australia and check Pipedrive's own pricing page for the current AUD amount and GST treatment.

Automations or Sequences: Which Should You Use?

I'd use Automations for a rule tied to a record change: send an acknowledgement, check for a reply and create a call activity. I'd use Sequences for a planned series of emails and tasks that a salesperson works through.

See email conditions and Sequences. As at 10 October 2026, each sequence supports up to 15 steps and 250 enrolled leads or deals. Pipedrive's documentation does not establish that replies automatically stop a sequence, so include a deliberate stop process.

How Do You Set Up a No-Reply Follow-Up After Three Days?

The trap is waiting for a reply and expecting expiry to send the next email. Pipedrive stops the automation when the wait condition expires. Build and test the no-reply branch explicitly.

1. Name the trigger. Choose the creation or update event that starts follow-up. The Nurture new leads template is a starting point. Check how records enter Pipedrive: imports do not fire event-triggered automations.
2. Gather the data. I'd require an email address, owner, enquiry details and a clear next action. Set up email sync and create the email template in Sales Inbox. Link merge fields to the relevant lead, deal, person or organisation.
3. Prepare the follow-up. Send the initial template, add a three-day delay, then evaluate whether that automation's email received a reply. Use if/else branching: the reply path ends follow-up; the no-reply path sends another template or creates a call activity. Reply checks concern the previous automated email, not an unrelated manual or bulk email.
4. Choose who approves. If the message needs judgement, create an activity for the owner instead of sending automatically. Alternatively, use a Sequence draft email step that appears in Pulse for the salesperson to handle.
5. Record and test. I'd record the next activity and outcome against the lead or deal, then test both reply paths with controlled records. Check that an answered enquiry does not receive the no-reply message.

What Are the Limits and Gotchas?

As at 10 October 2026, Pipedrive's limits include up to ten actions per automation, seven days per wait-for-condition step, 90 days of total delay and 40 email actions per minute across the company account. Gmail and Outlook also apply their own sending limits.

• Opens cannot drive conditions. Email opening tracking is unsupported for automation conditions; link clicks can be used.
• Email sync matters. Automated emails require email sync. Test the intended sender's account.
• Sending authorisation is individual. Each user authorises automated and delegated sequence sending. Removing authorisation after scheduling causes that email step to fail.
• Sender authorisation differs from recipient consent. For Australian marketing emails, check the ACMA guidance on consent, sender identification and unsubscribe requirements. Treat an enquiry response separately from promotional nurture. This is general information, not legal advice.

For reminders, activity notifications can surface the follow-up task. I'd give every task an owner; a reminder without someone responsible still leaves the enquiry sitting there.

When Do You Need Zapier, Webhooks or the API?

Use a connection when Pipedrive lacks information needed for the next action. Zapier's Marketplace listing describes capturing information from other apps, including creating deals from Typeform entries.

For a fuller design, a Pipedrive webhook notifies a workflow when a lead or deal changes. The workflow gathers the enquiry, suburb, service, previous correspondence and quote details; prepares a relevant message; holds it for approval; then uses the API to record a note, activity or stage update.

I'd also build checks for replies, opt-outs and duplicate events before sending. Those are requirements for the connected design, not automatic promises from the webhook.

How Do You Keep a Person Approving Important Follow-Ups?

For native review, use Sequence draft steps. For AI assistance in the composer, Write my email is available on Premium and higher under the current plan mapping, as at 10 October 2026. A person edits and sends the draft; the documentation does not connect AI drafting to Automations.

I'd hold messages involving a disputed quote, a strained relationship or an uncertain promise. Routine templates can follow agreed rules; sensitive follow-ups need someone to read the context.

For an Australian service business that wants follow-up automation built around its existing Pipedrive and then run for it, with a person approving anything sensitive, Truespeak is built for exactly that. Truespeak designs, builds and manages lead follow-up automation, including monitoring failures and reviewing exceptions after launch. I've built this pattern before outside Pipedrive: a sister build to Truespeak's Agent Helper pulls old leads from a real estate CRM each week and drafts a three-email sequence held for approval.

If you want that connected layer scoped, start with a discovery call. If you're comparing platforms or implementation help, see my HubSpot follow-up guide and Australian Pipedrive consultant guide.