Not from the reports screen — there's no way to set a report to run and email itself weekly or monthly. There are two things that come close, and they're worth telling apart because they often get mixed up.
What you can do today
Save the report and re-run it. Build the report with the filters and columns you want, save it with a name you'll recognise, and open it from the Reports tab whenever you need it. Change the date range and click Create Report — usually quicker than it sounds, and it's the route most teams use for a monthly pull.
Download and share the output. Each run gives you a PDF or CSV download you can attach to an email or drop into your own shared drive.
Run reports programmatically. Report execution is available through the Gigwell API and through MCP, which lets a connected tool or assistant pull reporting data directly. This is switched on per account by our team rather than something you turn on yourself — start a chat from the messenger if you'd like it enabled for your account, and your developers can work from the public API documentation once it's on.
Settlement statements are a different thing
This is the distinction that causes most of the confusion. Settlement statements can be emailed automatically, and that's a notification, not a scheduled report.
To set that up, go to Settings > Notifications and configure the settlement statement notification. It sends a statement when the event it's tied to happens — it doesn't run a report on a timetable.
So: statements going out automatically after settlement is available. A Bookings or Events report landing in your inbox every Monday morning is not.
Good to know
Naming saved reports for what they contain — the agent, the artist, the period — makes a monthly re-run much less work, because you're picking from a list rather than remembering how each one was built.
If a recurring emailed report is something your team needs, tell us what you'd want in it and how often. Start a chat from the messenger and we'll pass it on.
API and MCP access is granted account by account, so if a colleague has it, it doesn't automatically mean your account does.