EspoCRM has a real workflow engine under Administration → Workflows: triggers on record events and schedules, conditions, and actions like sending email, creating records, or applying assignment rules. Add scheduled jobs and a REST API, and most automations you would sketch on a whiteboard can be built by the agent while you describe them. Here are ten worth building.

1. Nudge owners about stale deals

Deals die quietly when nobody looks at them for two weeks. A scheduled workflow can check opportunities every morning, find the ones whose stage has not changed in seven days, and email the owner a reminder with a follow-up task attached. Say “Every morning, find opportunities that haven’t moved in 7 days, email the owner, and create a follow-up task due today.” The first week usually surfaces deals everyone assumed were fine.

2. Route new web leads to a human in seconds

A lead that waits four hours for a reply is a lead half lost. Wire a workflow to the lead-capture form: when a lead is created with the web-form source, assign it round-robin across the Sales team, post a stream notification, and send the auto-reply template so the lead gets an instant answer. Say “When a lead comes in from the web form, assign it round-robin to the Sales team and send the intro email template.” Response time drops from hours to minutes without anyone watching a queue.

3. Chase every proposal automatically

Proposal follow-up is the cheapest revenue in sales and the first thing that slips when the week gets busy. A workflow on stage change can do it for you: when an opportunity moves to Proposal Sent, create a follow-up task three days out and queue the nudge email; a second workflow sends the firmer version after a week of silence. Say “When an opportunity moves to Proposal Sent, schedule a follow-up task three days later, and if there’s still no reply after seven days, send the follow-up template.” Nothing falls between desks.

4. Win back lost deals on a schedule

Closed Lost is not always forever — it often means “not this quarter.” A workflow can watch for the stage change to Closed Lost, add the contact to a Win-back target list, and create a call task 90 days out, so the account gets touched while the door is still open. Say “When an opportunity is closed lost, add the contact to the Win-back target list and create a task to call them in 90 days.” Paired with a campaign, that list becomes a quarterly reactivation push instead of a graveyard.

5. Escalate support cases that sit too long

Customers judge you on how fast the first human answer arrives, not on what your website promises. A scheduled workflow can find cases that are still New with High priority after four hours, flip them to Escalated, and email the support lead the list. Say “Every hour, escalate any case that has been New with High priority for more than 4 hours — set it to Escalated and email the support lead.” An SLA you actually enforce beats one you only advertise.

6. Onboard every new customer the same way

After Closed Won, a dozen small things must happen: welcome the customer, brief the person who owns the relationship, schedule the kickoff. A workflow on stage change can send the welcome template, create the onboarding task for the account owner, and drop the account into a New Customers target list. Say “When a deal is closed won, send the welcome email, create an onboarding task for the account owner, and add the account to the New Customers list.” Every customer gets the same solid start, not whatever the week allowed.

7. Remind owners before deals are due to close

Expected close dates quietly pass when nobody is watching, and the forecast turns into fiction. A scheduled workflow can look ahead 30 days, and for every opportunity closing this month create a task and email for the owner: confirm the date or move it. Say “Create a check-in task and email the owner 30 days before each opportunity’s expected close date.” Forecast reviews stop being arguments with the spreadsheet.

8. Push contacts to your newsletter tool every night

EspoCRM is your source of truth for contacts, but it is not where you send newsletters. A small script using Espo’s REST API — reading contacts with a Newsletter tag and upserting them into listmonk, Mailchimp, or similar — plus a nightly scheduled job keeps the two in sync. The agent can write it, test it on real records, schedule it, and log failures somewhere you will see them. Say “Every night, push contacts tagged Newsletter to our listmonk list over the REST API, and log any failure.” No more export-CSV-upload rituals.

9. Alert the team chat when a big deal moves

Email alerts get ignored; chat messages get seen. The agent can set up a small scheduled job that asks the Espo API for opportunities over a threshold that recently entered Negotiation, and posts a message to your Rocket.Chat or Slack webhook. Say “Post to our Rocket.Chat sales channel whenever a deal over $10,000 enters Negotiation.” It is glue code the agent writes and maintains, and all you do is read the channel.

10. Cool down leads that have gone quiet

A database full of “warm” leads nobody has touched in two months poisons your reporting and your morale. A nightly scheduled workflow can find leads with no activity in 60 days, move them to a Cold status, and notify the owner so the list stays honest. Say “Every night, mark leads with no activity in 60 days as Cold and tell the owner.” Your pipeline numbers start meaning something, and your reactivation campaigns finally get a real audience.

See it in action

Official walkthroughs from the EspoCRM team:

Worth a watch next:

• Export reports to Excel format in EspoCRM — scheduled report delivery, a natural companion to the automation ideas above.
• Reports and Analytics in EspoCRM — the reporting engine your workflows can feed every Monday morning.

Start with one workflow and watch it for a week before chaining more — conditions and actions are easy to tweak once you see real traffic. The agent can also trace why a workflow did or did not fire on a given record, which is half the battle with any automation tool. If you need the server itself, it is here: EspoCRM on OpenSysLab.