Introduction
What are Webhooks?
Webhooks are a lightweight, developer-friendly way to receive real-time notifications when specific events occur in UseStencil. Instead of constantly polling an API to check for updates, webhooks push event data to your specified URL the moment something happens — in this case, when a new image is created.
They enable seamless communication between UseStencil and your external systems, so you can automate workflows, trigger downstream processes, or log activity with minimal effort.
If you are interested in reading and learn more about Webhook, consider visiting this excellent article on Webhook from Zapier. Come back here when you're done!
How Webhooks Work in UseStencil
When your workspace generates a new image — whether through automated actions, user requests, or scheduled jobs — UseStencil triggers a image.created
event. A JSON-formatted payload is immediately sent to the URL you’ve configured in your Webhook settings.
This allows your application or third-party service to respond in real-time. Whether you’re sending notifications, updating a database, or syncing with another app, webhooks help bridge that gap efficiently.
Basic Workflow
Image Created in UseStencil → Webhook Triggered → Payload Delivered to Your Endpoint.
You may have multiple webhooks being set up for one template
Key Benefits
⚡ Instant Notifications
Get real-time updates the moment an image is generated
🔗 Seamless Integration
Connect with external tools (Slack, storage APIs, automation platforms)
📦 Simple Payloads
Easy-to-parse JSON data ready for immediate use
🔐 Secure Delivery
Optional secret token to verify the source of incoming requests
Real-World Use Cases
Even with a single event type, image.created
unlocks powerful workflows:
Internal Automation: Automatically upload new images to your image CDN or S3 bucket.
Notifications: Post a generated image to a Slack channel or Discord server with metadata.
Processing Pipelines: Trigger additional tasks like watermarking, resizing, or captioning via serverless functions.
Analytics: Track how often and when images are being generated for reporting or audit purposes.
Who Should Use This?
This feature is ideal for:
Developers who want to trigger custom actions on image creation
Ops & Automation Engineers needing system-wide image notifications
Teams using third-party tools like Zapier, n8n, or Make to handle image delivery, archival, or routing
You! no, seriously
✅ Next Up: Getting Started with Webhooks
We’ll walk you through how to enable webhooks, configure your endpoint, test it, and start receiving image.created events.
Last updated
Was this helpful?