How to Get Notified When Media and AI Summaries Are Ready in Custom Storage

Overview

Blitzz pushes session media (recordings, images, files, and AI Call Summaries) to your custom storage endpoint once a session completes and processing finishes. Since these files arrive directly in your own cloud account, the easiest and most reliable way to know when something new is ready is to use the native event notification system from your cloud provider.

Blitzz does not currently provide a webhook for individual file availability. Custom webhook implementations can be discussed with your account team, but the cloud native options below are immediate, low cost, and give you full control on your side.

This article covers two setups:

• Azure Blob Storage using Azure Event Grid
• AWS S3 using S3 Event Notifications

Who is this for?
Customers using Blitzz with a custom storage endpoint (Azure Blob or AWS S3) who want to be notified the moment a new recording, image, or AI summary lands in their bucket or container.

---

Option 1: Azure Blob Storage with Event Grid

If your custom storage endpoint is an Azure Blob container, Event Grid can fire a Microsoft.Storage.BlobCreated event the moment Blitzz writes a new file to your container. You can route that event to an Azure Function, a Logic App, a webhook URL on your side, or any other supported handler.

What you get

• Instant notification when a file is created in your container
• The ability to filter by container, file path prefix, or file extension (for example, only fire on AI summary files)
• No polling required

Setup steps

1. Sign in to the Azure Portal and open the Storage Account that Blitzz is configured to push to.
2. In the left menu, click Events.
3. Click + Event Subscription.
4. Give the subscription a name (for example, blitzz blob created).
5. Under Event Types, select Blob Created. You can deselect the others if you only care about new files.
6. Under Endpoint Type, choose where to send the events:
   • Azure Function for custom processing logic
   • Webhook to post to your own HTTP endpoint
   • Logic App for low code workflows
   • Event Hubs, Service Bus, or Storage Queue for queued processing
7. (Optional) Under Filters, narrow the events. For example:
   • Subject begins with /blobServices/default/containers/your_container_name/blobs/
   • Subject ends with .json if you only want AI summary files
   • Subject ends with .mp4 if you only want recordings
8. Click Create.

What the event looks like

A Blob Created event payload includes the blob URL, container name, file size, content type, and the API call that wrote it. Your handler can pull the file directly from the URL or trigger a downstream sync to another system.

Reference

Azure Blob Storage events: https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview

---

Option 2: AWS S3 with S3 Event Notifications

If your custom storage endpoint is an AWS S3 bucket, S3 Event Notifications can fire on every s3:ObjectCreated:* event. You can route the event to SNS, SQS, Lambda, or Amazon EventBridge.

What you get

• Real time notification when Blitzz uploads a new object
• Filtering by prefix (folder path) and suffix (file extension)
• Fanout via SNS or queued processing via SQS
• Direct Lambda execution if you want to process the file immediately

Setup steps using the AWS Console

1. Sign in to the AWS Console and open S3.
2. Click the bucket that Blitzz is configured to push to.
3. Go to the Properties tab.
4. Scroll down to Event notifications and click Create event notification.
5. Give the notification a name (for example, blitzz object created).
6. (Optional) Under Prefix and Suffix, narrow which objects trigger the event:
   • Prefix example: sessions/ to only listen for files under that folder
   • Suffix example: .json for AI summaries, .mp4 for recordings, .jpg for images
7. Under Event types, select All object create events (or pick specific ones like Put and Multipart upload completed).
8. Under Destination, choose one of:
   • Lambda function for custom processing
   • SNS topic for fanout to multiple subscribers, including email or HTTPS endpoints
   • SQS queue for reliable queued processing
9. Select the destination resource and click Save changes.

Routing to a webhook on your side

S3 cannot post directly to an HTTPS endpoint, so the typical pattern is:

• S3 to SNS to HTTPS: create an SNS topic, subscribe your HTTPS endpoint to it, and confirm the subscription. SNS will then POST every event to your URL.
• S3 to Lambda to your endpoint: write a small Lambda that receives the S3 event and calls your internal API.
• S3 to EventBridge: enable EventBridge on the bucket and use rules to route events to dozens of supported targets, including API Destinations for any HTTPS URL.

What the event looks like

An S3 ObjectCreated event payload includes the bucket name, object key, object size, ETag, and the event time. Your handler can use the key to generate a presigned URL or sync the file elsewhere.

Reference

AWS S3 Event Notifications: https://docs.aws.amazon.com/AmazonS3/latest/userguide/EventNotifications.html

---

Tips and best practices

• Filter aggressively. A typical Blitzz session writes multiple files (recording, images, AI summary). If you only care about one type, filter by file extension or path prefix so your handler is not flooded.
• AI summary timing. AI Call Summary files are written after the session ends and post processing completes. If you depend on the summary specifically, listen for the summary file extension or path rather than the recording, since they arrive at different times.
• Idempotency. In rare cases an event may be delivered more than once. Make your handler safe to run twice on the same file.
• Test with a real session. The simplest way to validate your setup is to run a test Blitzz session, let it complete, and watch the event fire in your handler logs.

---

Still need help?

If you have configured your storage endpoint with Blitzz and are not seeing files arrive, or if you need help choosing between Event Grid, SNS, SQS, or Lambda for your use case, please submit a support ticket and our team will help you set it up.