# Pipedrive has no recurring activities: three workarounds for quarterly check-ins

https://salesbond.app/blog/pipedrive-recurring-activities-workaround/
Published: 2026-10-05 · Updated: 2026-10-05

Pipedrive does not have a feature for recurring activities. The closest options are recurring events synced from your calendar (they show up in Pipedrive but can only be edited in the calendar), a date-triggered automation that creates an activity off a date field you maintain, or a saved filter you review on a fixed day instead of an activity. Which one to pick depends on what breaks when a person forgets, not on which is most elegant. This article is about the recurring rhythm after the sale: the quarterly call with an existing customer, the monthly check on a renewal account. For the cadence of touches on open deals, see [sales cadence for a small team](https://salesbond.app/blog/sales-cadence-small-team-pipedrive/).

## “Every quarter, call this customer” is a rhythm, not a task

A sales manager asks for recurring activities because she has twelve accounts that each need a call every quarter, and she wants Pipedrive to remind the rep. Fair. But look at what she is actually describing.

It is not one task that repeats on the same date forever. It is a rhythm that belongs to the customer: the call happens roughly three months after the last call, and the last call moves. If the rep reaches the customer two weeks late, the next one should be three months after that, not on the original schedule. If the customer buys early, the rhythm resets.

A repeating task cannot carry that. A repeating task is a metronome, and a customer is not. Seen this way, the missing feature matters less, because two of the three workarounds below handle the moving date, which a fixed repeat never could. The third is the fallback for a team that will not maintain a date field no matter how many times you ask.

So the question we start with is: who moves the date after each call, and what happens if nobody does?

## What the help center says, in one sentence

Pipedrive’s own article on recurring activities says there is no dedicated feature, and that the way to get a repeating activity is to sync it over from an external calendar ( [Pipedrive: Recurring activities](https://support.pipedrive.com/en/article/recurring-activities)). The calendar sync article puts it more plainly: “Currently, it’s not possible to create recurring activities in Pipedrive” ( [Pipedrive: Calendar sync](https://support.pipedrive.com/en/article/calendar-sync)). No hidden toggle, then. Search results also point to paid third-party schedulers such as Zapier; that is a fourth path, and we leave it out on purpose.

## Path 1: the repeat lives in your calendar, and shows up gray

This is the path the help center points to, and for one specific case it is the best one. Create the recurring event in Google Calendar or Outlook, invite the customer, and let calendar sync bring it into Pipedrive. The rep gets the reminder in the tool he actually looks at all day, the customer has it in thier calendar too, and the meeting shows up in Pipedrive as an activity.

The catch is in the color. Recurring activities that come in from your calendar provider appear gray in Pipedrive and cannot be edited there; if you want to move one, you move it in the calendar ( [Pipedrive: Recurring activities](https://support.pipedrive.com/en/article/recurring-activities), [Pipedrive: Calendar sync](https://support.pipedrive.com/en/article/calendar-sync)). You can delete one from Pipedrive, but you cannot drag it to next Tuesday from the activities list.

In practice the rep lives in two places: Pipedrive for notes and the deal, the calendar for the schedule. That works for a fixed-cadence review with a customer who shows up to it, say a monthly account meeting that both sides have in their calendars. It works badly for the quarterly “let’s catch up” call that gets rescheduled twice before it happens, because every reschedule is a calendar edit and Pipedrive just follows along.

Which calendar is synced, and whether private events come across, also decides whether this path fits you. We covered those settings and what they do to your meeting numbers in [Pipedrive calendar sync: when every event becomes a meeting](https://salesbond.app/blog/pipedrive-calendar-sync-meetings-activities/). Short version: if you put a recurring customer event in a synced calendar, make sure it is the calendar you meant.

## Path 2: a “Next check-in date” field and a date-triggered automation

This is the path for the moving date. Instead of asking Pipedrive to repeat anything, you keep one fact per customer, the date of the next check-in, and let an automation turn that date into an activity when it gets close. Date triggers are part of Automations and are available on the Growth plan and higher; they work for activities, deals, organizations and people ( [Pipedrive: Date triggers](https://support.pipedrive.com/en/article/automations-date-triggers)).

Here is the setup for a quarterly customer call, built on the organization.

1. Create a custom field on the organization of type **Date** and call it something like “Next check-in date”. The type matters: when you later pick a field for the date trigger, the dropdown shows only Date-type fields ( [Pipedrive: Date triggers](https://support.pipedrive.com/en/article/automations-date-triggers) ).
2. Fill the field for the accounts that need a rhythm. Twelve accounts is twelve dates. Do this once, by hand, and decide who owns it; the field is the the whole system.
3. Create an automation with the **Date trigger** on the organization, pointing at that field. Pick the organization deliberately: once the trigger is created, you can’t switch it to a deal or a person ( [Pipedrive: Date triggers](https://support.pipedrive.com/en/article/automations-date-triggers) ). You choose **Exact date**, **Before date** or **After date**, and the before/after offset goes up to 180 days. For a quarterly call, “Before date, 7 days” gives the rep a week of runway; “Exact date” gives none.
4. Set the hour and the time zone the trigger should run at; both are part of the trigger ( [Pipedrive: Date triggers](https://support.pipedrive.com/en/article/automations-date-triggers) ). We pick a weekday morning in the rep’s own time zone.
5. Add the action: create an activity. The automation can set a relative due date such as “In one day” or “next Tuesday” ( [Pipedrive: Workflow automation](https://support.pipedrive.com/en/article/workflow-automation) ), so the task can land on the day you want the call made rather than the day the trigger fired.
6. If several reps own accounts, enable the automation for them: when a date trigger is enabled for multiple users, it checks the items of all enabled owners ( [Pipedrive: Date triggers](https://support.pipedrive.com/en/article/automations-date-triggers) ). One automation covers every rep’s accounts.

![Timeline: a date trigger fires seven days before the Next check-in date, creates a call activity, and the rep sets the next date by hand](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-recurring-activities-workaround-2.png)

The part that is easy to miss: the date trigger only reads the field. The help article describes what happens before, on or after that date. It says nothing about writing the next date into the field once the call is done. So after the rep makes the call someone has to open the organization and set “Next check-in date” three months out. If nobody does, the rhythm stops silently. No error, no overdue task, just an account whose date is in the past and an automation with nothing left to fire on. Say that at the planning meeting, not in month five.

Our rule for the field: the rep who marks the call activity as done sets the next date in the same minute. Not the manager later, not “the automation will handle it”. Its one field and it takes ten seconds. A manager can spot-check it with a filter on the organization list for empty or past dates, which is close to the list you would build for [inactive customer accounts](https://salesbond.app/blog/pipedrive-inactive-customers-accounts-filter/).

Two cautions about automations in general, both covered elsewhere. Automations run under an owner, and a trigger enabled for a user who has since left keeps or loses its behavior depending on how you handle their account; that is the subject of [the automations owner audit](https://salesbond.app/blog/pipedrive-automations-owner-audit/). And every plan has ceilings on automations and the delays inside them, which we went through in [when a follow-up automation quietly stops](https://salesbond.app/blog/pipedrive-automation-limits-follow-up/). A date trigger needs no delay step at all, which is one reason we prefer it to a chain of waits for this job.

## Path 3: skip the activity, open a list on Fridays

Sometimes the team simply will not maintain a date field. Nobody is proud of it, but a four-person team with one rep covering accounts has limited patience for one more field, and a workaround that depends on discipline nobody has is worse than no workaround.

For that team, do not create an activity at all. Create a saved filter of customer organizations, name it something like “Accounts: check-in review”, show the **Last activity date** column (the date of the last activity marked as done) and sort it oldest first. Then put a fifteen-minute slot on the manager’s calendar every Friday to open it. How to build that filter so it actually finds lapsed customers is in [inactive customers and accounts](https://salesbond.app/blog/pipedrive-inactive-customers-accounts-filter/); here you only need the list. The manager picks the three accounts that have been silent longest and books a call for each one right there, as a single ordinary activity. Once those calls are marked done, the three drop to the bottom and next Friday’s top rows are someone else.

This path replaces the automation with a habit and the field with a glance. It scales badly past a few dozen accounts and it depends on one person’s Friday. But it has no silent failure mode: if the manager skips a Friday, everyone knows, because the slot is on the calendar. When the list gets long enough to hurt, you can create the batch of calls in one go, which is what [bulk activities for a follow-up batch](https://salesbond.app/blog/pipedrive-bulk-activities-follow-up-batch/) covers.

## Which path for which job

A standing monthly meeting the customer also attends belongs in the calendar. Reschedules happen there and Pipedrive only mirrors them, but when it fails you can see it: the gray event is still sitting in the list.

A quarterly call whose date moves after every conversation is Path 2. It is the only one of the three that follows the customer’s rhythm, and the only one that fails quietly, with a past date and no new activity. Choose it if someone will own the field.

For a small account base and a team that will not keep a field, use the Friday list. It fails loudly too.

If your renewals run on a contract date rather than a conversation rhythm, the date already exists in some form and Path 2 is the obvious fit; we walk through that case in [the customer renewal process in Pipedrive](https://salesbond.app/blog/customer-renewal-process-pipedrive/). Can’t decide? Start with Path 3 for a month. It costs nothing to set up, and it tells you whether the team will actually make the calls, which is the question a recurring activity would have hidden anyway.

## Where SalesBond fits

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Customer Health ignores reminders and date fields and reads purchase history instead: each repeat customer is on track, overdue or leaving depending on how long it has been since their last won deal compared with their usual gap between purchases. That surfaces the account whose check-in date nobody moved, but it books no calls; one of the three paths above still has to do that. If you want to know which accounts have already slipped before you pick one, [check your CRM with SalesBond](https://salesbond.app/).