This section is for advanced users comfortable with API integration and automation workflows. If you’re just getting started with Renderjuice, the dashboard provides everything you need for rendering.
When to customize
Consider leveling up your pipeline if you want to:- Eliminate manual steps – stop polling job status or dragging files around.
- Connect your tooling – plug Renderjuice into Slack, Ftrack, ShotGrid, Premiere, or internal utilities.
- Build conditional workflows – run quality checks, fork jobs, or route outputs based on metadata.
- Stay informed automatically – get notified (or trigger retries) the moment something succeeds or fails.
How to extend Renderjuice
When deciding which tool to use, follow this progression:1
Use the dashboard first
Most rendering needs are already supported in the UI. Even if you plan to customize, start with the built-in controls to offload as much orchestration as possible.
2
Add webhooks for reactive flows
Webhooks are low-effort and require little to no code. They cover the majority of “tell my tools when X happens” workflows.
3
Layer in the API for full control
When you need to submit jobs programmatically, bulk-manage resources, or coordinate across multiple systems, reach for the API. Many teams combine both webhooks and API calls for end-to-end automation.
Proactive vs Reactive: understanding the difference
The fundamental distinction is who initiates the interaction.Webhooks: reactive automation
Renderjuice notifies you instantly when events happen. No polling, no waiting—your systems respond automatically.API: proactive control
You decide when to act. Call Renderjuice to create jobs, query status, or manage resources on your timeline.Combined: the most powerful approach
Use the API to control what happens on Renderjuice, webhooks to react to outcomes. Together they enable fully automated, event-driven pipelines.Use Cases
Webhooks: react to events
When render milestones occur (job completion or failure), Renderjuice sends signed payloads to your endpoints so your systems can respond instantly — no polling required. Best for:- Notifications and status alerts when jobs succeed or fail
- Auto-delivering rendered outputs to storage (Google Drive, Dropbox, S3, on-prem)
- Triggering downstream processes (compositing, encoding, QC, ingest)
- Logging and analytics feeds
- Low-code automation with Zapier, n8n, Make, Airplane, or Retool
API: programmatic control
The API gives you direct control over Renderjuice—submit jobs, query status, and coordinate multi-stage workflows from your own systems. Best for:- Submitting renders from DCC tools (Blender addons, Maya scripts, custom exporters)
- Bulk operations across multiple jobs or projects
- Building custom dashboards for monitoring and triaging
- Multi-stage workflows with conditional rendering
- Deep integrations or marketplace apps
Using them together
The most powerful pipelines combine both channels: webhooks notify you when events occur, and the API lets you react programmatically. Example workflow:- Receive an
onRenderFailwebhook with the job ID and failure reason - Call the API to fetch job metadata and analyze the failure
- Use the API to queue a new job with adjusted render settings
- Trigger a Slack notification that a retry is in flight
Getting started
Most studios begin with simple webhook-driven notifications or file delivery. As workflows mature, they layer API calls for submission, retries, or resource management. Both webhooks and the API work well with low-code orchestrators (Zapier, n8n, Make, Airplane, Retool) so you can iterate quickly without rewriting your entire pipeline. Ready to dive in? Check out the detailed guides:- Webhooks guide – Learn how to set up reactive automation
- API guide – Explore programmatic control options
- API Reference – Technical documentation for implementation