Skip to main content

How to schedule Flow Monthly in Salesforce

About Us
Published by jetbi
19 March 2021
4136

 

Sometimes managers need to schedule Salesforce flows on monthly basis to review existing processes in the enterprise and create business strategies for the future. Unfortunately, for now, there is a limitation in Salesforce, you can schedule a Flow only once, daily or weekly. Often business needs are focused on the long-term perspective so the task to schedule Salesforce Flow monthly appears quite often. Have your admins ever wondered how to do it?

flow-monthly-1

Here is a solution JET BI Salesforce Admins and Consultants use when such a need arises. Here we go.

 

1) Firstly, you should create a custom setting, where you will need to create a new custom setting and create a new Custom Field (Data Type - Number (2,0)).

flow-monthly-2

 

flow-monthly-3

 

2) Secondly, you should choose an object’s record that will trigger the Flow.
In our case, this is an Opportunity. On Opportunity, we should create a new custom field (Formula boolean).

flow-monthly-4

 

This formula will be set to TRUE when our value in custom settings will be equal DAY(TODAY)
Formula: DAY(TODAY())= $Setup.Bonus_Manager__c.Start_Flow_Date__c

 

3)After creating your Flow, you should Set a Schedule Daily, and choose Opportunity with Monthly_Schedule__c = TRUE

flow-monthly-5

 

flow-monthly-6

 

You can use this solution in any business case when you need to schedule flow monthly. In our case, we used the logic to calculate bonuses on a monthly basis.

 


Julia Gaidalenok
Project Manager
image
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026