Eodly Zapier integration: send your evening report anywhere
Eodly is in the Zapier app directory. Once it is connected, every new evening report can start an automation: add a row to a Google Sheet, post to a Slack channel your team actually reads, save a page in Notion, or email it to a co-founder or an investor.
The integration is read-only. Zapier can read your reports and nothing else, and it cannot change anything in Eodly.
Connect Eodly to Zapier
- In Zapier, create a new Zap and choose Eodly as the trigger app. You can also start from the Eodly page on Zapier.
- Pick the New Report trigger.
- Click Sign in (Zapier may label it Connect). An Eodly page opens: sign in with your Eodly account, check what Zapier is asking for, and choose Allow.
- Test the trigger. Zapier pulls your recent reports as sample data.
- Add the step that sends the report where you want it, map the fields, and turn the Zap on.
Only a founder or lead of the workspace can connect it. It works on every Eodly plan, including Free, and it does not need an API key.
When it runs
Eodly writes the report at the time set in Settings, under Report time. Zapier checks Eodly for new reports on a regular interval, so the Zap runs within that interval after the report is ready. How often Zapier checks depends on your Zapier plan.
Each report starts the Zap once. A report Zapier has already seen never runs it again.
Which reports start the Zap
Every report your workspace gets is a new report, and each one has a scope:
| Scope | What it is |
|---|---|
org |
The main evening report for the whole workspace |
lead |
A team lead's report, scoped to their own team (only if you turned on lead reports) |
investor |
An investor update (only if you send them) |
Most workspaces only get the org report. If yours also gets lead or investor reports and you only want the main one, add a Filter by Zapier step after the trigger: continue only if Scope exactly matches org.
The fields you get
| Field | What it holds |
|---|---|
report.headline |
The one-line summary at the top of the report |
scope |
Which kind of report it is (see above) |
generated_at |
When the report was written |
report.shipped |
What got done: who, what, and the evidence behind it |
report.slipping |
Claims that the evidence does not back up yet |
report.blockers |
Who is blocked and on what |
report.silent |
Who neither checked in nor showed any activity |
report.quiet |
Who had real activity but did not check in |
report.kpi_status |
Where each KPI stands today |
id |
The report's id in Eodly |
Lists such as report.shipped arrive as line items, one per entry. When you map a list into a single text field, like a Slack message or an email body, Zapier joins its entries with commas.
Disconnect
In Eodly, open Settings, then the Developer tab, and look under Connected apps. Disconnecting Zapier stops its access straight away, and any Zap using Eodly stops until you sign in again.
When something is wrong
- The trigger test finds no reports. Your workspace has not had an evening report yet. Test again after the first one arrives at your report time.
- Zapier asks you to reconnect Eodly. Sign in again from the Zap's Eodly step. Your Zaps keep their settings.
- A Zap step fails after the Eodly step. Zapier's support team handles questions about Zaps and other apps at zapier.com/app/get-help.
- The report itself looks wrong. That is Eodly's side. The troubleshooting guide covers the common causes, or write to hello@eodly.io.
To read your reports from Claude or Cursor instead, use the Eodly MCP server.