Check out what I made: A simple Zapier flow for new summary alerts.

carlr · 2026-07-30T09:06:01Z

Noticed the new Read AI summaries are decent for spotting trends, but their in-app notifications are easy to miss. If you want a proper alert—something that can ping a Slack channel or create a ticket—you have to build it yourself. Here's a trivial Zapier flow that works. It polls the Read AI summaries feed via their webhook and pushes a formatted alert to a destination of your choice. The key is filtering for the "new_summary" event type. **Zap Trigger:** * App: Webhooks by Zapier * Event: Catch Hook * Use the provided URL in Read AI's webhook setup. **Filter (Essential):** * Only continue if... * `Event Type` (from the webhook data) `Text` `Exactly matches` `new_summary` **Action Example (Slack):** * App: Slack * Event: Send Channel Message * Channel: `#alerts` * Message Text: Constructed from the webhook data. ```json { "text": "New Read AI Summary", "blocks": [ { "type": "section", "text": { "type": "mrkdwn", "text": "*Summary for Meeting:* `{{webhook_data.meeting_title}}`n*Key Topic:* {{webhook_data.primary_topic}}" } } ] } ``` The webhook payload has the usual fields: `meeting_title`, `summary_url`, `primary_topic`, etc. It's straightforward. This at least gets the alert out of their walled garden and into a pipeline where you can actually act on it. - cr

Page 2 / 2 Prev

Read AI Reviews

Last Post by Grace W 1 hour ago

16 Posts

16 Users

0 Reactions

4 Views

RSS

Grace W

(@gracew23)

Active Member

Joined: 1 day ago

Posts: 11

31/07/2026 12:34 am

Exactly. Missing the summary_url field means the alert is broken on arrival. The operational waste is immediate: someone gets the notification, then has to stop, open Read, and manually search for the thing they just got alerted about.

That isn't automation, it's a distraction. If the payload in the post is wrong, the whole setup is a guide to a dead end.

Trust, but audit.

ReplyQuote

Page 2 / 2 Prev