Can Your FileMaker Do This? Email Scheduled PDF and Excel Reports Automatically

Yes. FileMaker scheduled reports can run entirely on FileMaker Server: a server schedule finds the right records, saves them as a PDF or Excel file, and emails that file to the people who need it, with no one pressing a button. The details that make it reliable are server compatibility, file paths, and logging.

Picture an operations manager on a Monday morning. Before the sales meeting, she opens FileMaker, finds the open orders, saves a PDF, and types six addresses from memory. If she is out sick, the meeting runs on last week’s numbers.

The report exists; the routine around it is the problem

Most FileMaker systems already have the layout. What does not scale is the human routine wrapped around it.

Someone has to remember the day, run the right find, and know who gets the file this month.

A scheduled report removes all three. A basic flow might look like this:

FileMaker Server schedule fires at 6:00 AM

↓

Server-side script finds and sorts the records

↓

Script saves the found set as a PDF or Excel file

↓

Script looks up who should receive it

↓

Send Mail delivers the file through SMTP

↓

Script writes a log record: sent, failed, or skipped

If you already build reports in FileMaker, as in our walkthrough on building year-end profit and loss reports directly in FileMaker, this is the delivery layer.

How does FileMaker Server run a report on a schedule?

In Admin Console (the browser-based FileMaker Server administration tool), you create a schedule of type FileMaker Script. Claris documents that you choose the hosted database, the script, the FileMaker account the script runs under, and when it runs. Repeat options are Once, Daily, Weekly, and Every N Days, with an optional end date.

If a run is still going when the next one is due, FileMaker Server skips the second run, and you can set a timeout so a hung script ends on its own.

There is no monthly option. For a month-end report, schedule the script daily and have it exit unless today is the last day of the month. A test such as Day ( Get ( CurrentDate ) + 1 ) = 1 handles that.

Which script steps work on the server, and which do not?

This is where first attempts break. A script that works from a button in FileMaker Pro can skip steps on the server. Claris lists compatibility on each step’s help page:

• Save Records as PDF: partially supported. With dialog: On, Automatically open file, and Create email with file as attachment are not supported on the server. In current versions, the step can save to a file path, a container field, or a variable.
• Save Records as Excel: not supported on FileMaker Server. Use Export Records with the Excel Workbooks (.xlsx) file type instead. Claris notes that server-side Export Records cannot write .fmp12 files and can only write to permitted folders.
• Send Mail: partially supported. Server-side scripts can send via SMTP or OAuth 2.0, but not through an email client such as Outlook on someone’s desktop.

Claris also advises that the layout’s fonts be installed on the server, or the PDF will not render them correctly.

File paths: the Documents folder and the temporary folder

Server-side scripts can only read and write in the FileMaker Server Documents folder or the temporary folder, plus their subfolders. Paths containing “..” are invalid.

• Get ( TemporaryPath ) returns a folder for that script’s session, deleted when the script finishes. Use it for a file you create and send in the same run.
• Get ( DocumentsPath ) returns the server’s shared Documents folder. Use it when a later script or another process needs the file.

A short sketch of the core steps (illustrative; exact options vary by version):

Set Error Capture [ On ]

Go to Layout [ “Open Orders Report” ]

Perform Find [ Restore ]

Sort Records [ Restore ; With dialog: Off ]

Set Variable [ $path ; Value: “file:” & Get ( TemporaryPath ) & “Open Orders.pdf” ]

Save Records as PDF [ Save to: File ; $path ; With dialog: Off ; Records being browsed ]

Send Mail [ Send via SMTP Server ; To: $recipients ; Subject: … ; Attach: $path ]

Set Variable [ $error ; Value: Get ( LastError ) ]

Pull recipients from data, not from the script

Hard-coded addresses break quietly. People change roles, contacts leave, and nobody remembers the script exists.

Instead, keep a Report Subscriptions table: report name, contact, email, active flag, and an optional filter (a rep who only wants their territory). The script finds the active subscribers and builds the To list from them. Claris documents that Send Mail accepts addresses separated by semicolons or returns, and can collect addresses across a found set.

Now the sales manager adds a new rep to the Monday report from a layout. No script edit.

Log every run, including the failures

A scheduled job that fails silently is worse than a manual one, because everyone assumes it ran. Give each run a record in a Report Log table:

• What and when: report name, run time, record count, file name.
• Who: the recipient list as sent.
• Outcome: Get ( LastError ) after the save and the send, with a status of sent, failed, or skipped (zero open orders, for example).
• The file, optionally, in a container field so someone can resend it.

Then have the script email an admin whenever a run logs failed or skipped, so nobody has to remember to check. FileMaker Server also records schedule results and skipped steps in its Event.log.

Where FileMaker scheduled reports usually fail

• Privileges. The schedule runs under the account you pick in Admin Console. Save Records as PDF needs the Allow printing privilege and exporting generally needs Allow exporting, unless the script runs with full access.
• Container and file paths. Files outside the Documents or temporary folders are not written, and temporary files vanish when the script ends.
• SMTP certificates. If the mail server’s SSL certificate cannot be verified server-side, Claris notes that Send Mail behaves as if canceled. Test against your real mail server.
• One-per-record sends. If one email fails in a one-per-record SMTP send, the rest are not sent. Loop and log each send instead.
• Time zones. A scheduled script reads the server’s clock. A hosted server set to UTC can make “yesterday’s shipments” the wrong yesterday, so calculate date ranges explicitly.

If your mail server is the weak link, our guide on sending emails from FileMaker using SendGrid covers an API-based alternative to SMTP, including attachments. Our post on sending calendar invites through FileMaker Pro shows another file FileMaker can generate and send.

Three reports worth scheduling first

• Weekly open orders (PDF). Monday at 6:00 AM to sales and customer service, with promised ship dates.
• Daily shipping summary (Excel). End of day to the warehouse lead and accounting as .xlsx, ready to reconcile.
• Month-end inventory value (PDF and Excel). Runs daily, exits unless it is month-end, then sends a PDF summary to the owner and .xlsx detail to the accountant.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help teams turn the reports they already run by hand into scheduled, logged deliveries on FileMaker Server.

Frequently asked questions

Can FileMaker Server email a report without anyone logged in?

Yes. A FileMaker Script schedule in Admin Console runs the script on the server under a FileMaker account you specify, and Send Mail can deliver through SMTP or OAuth 2.0 with no user session open.

Why does my Save Records as Excel step not work on the server?

Claris lists Save Records as Excel as not supported on FileMaker Server. Use Export Records with the .xlsx file type in server-side scripts instead.

Do I need a plug-in to schedule FileMaker reports?

Usually not. FileMaker Server schedules, the PDF and export script steps, and SMTP Send Mail are built in. A mail service such as SendGrid is optional if your own mail server gives you trouble.

Can your FileMaker email the Monday report before anyone is in the building? Bring the report your team rebuilds every week to a free 20-minute Data Health Check and we will show you what it takes to put it on a schedule.

P.S. Already know which reports you want automated? The 5-Hour Developer Assist Package gives you five hours with a Kyo developer to use any time within a year.