Start with the document.
Then trace the workflow.
Find the closest industry, team, or trigger to see how data becomes a reusable document or image workflow.
Free account, no credit card
By industry
Start with the records and documents already moving through your business.
E-commerce
Turn order and catalog data into confirmations, packing slips, and product images.
Read moreEducation
Create certificates, transcripts, and report cards from student and course records.
Read moreReal estate
Reuse property data across listing sheets, flyers, and documents that need the same facts.
Read moreBy role
Choose the team that owns the design, the data, or the delivery.
Marketing teams
Keep recurring social images, campaign reports, and branded assets tied to reusable designs.
Read moreDevelopers
Add document and image generation through a REST API or 8 official SDKs.
Read moreOperations
Generate invoices, shipping labels, and records from the systems where the work begins.
Read moreBy workflow
Start with the event that should create the file and the volume it needs to handle.
No-code automation
Use connectors and webhooks to create a document when another app records an event.
Read moreHigh-volume rendering
Queue larger runs, track their progress, and handle the result without holding one request open.
Read moreDynamic content
Merge a reusable design with new values when each recipient or record needs its own output.
Read moreUse-case questions, answered
Which use case should I start with?
Choose one recurring document with known input data and a result you can check. Build that template, run it with real examples, and review the output before expanding the workflow. The free account includes 50 renders and does not require a card.
Can one account cover several of these?
Yes. A workspace can hold templates, forms, and webpage captures for several workflows. Usage draws from the plan's render allowance rather than a separate allowance for each document type. The entry plan is $9 a month for 1,000 renders.
Do I need a developer to set this up?
Not for every workflow. The visual editor handles template design, while 732 connectors with 727 named actions cover supported app-to-app steps. Use the REST API or one of 8 official SDKs when the workflow belongs inside your own product.
How do these differ from each other in practice?
The main differences are the trigger, the input shape, and the number of files expected at once. A form begins with a submission. An API request begins in your application. A batch processes a larger set through a queued job. Each route can still use the same reusable template model.
Is somebody filling in a form counted as a user?
A public form respondent is not an internal workspace user. Plan limits on internal users apply to the people who work inside the account, such as template authors and administrators. Check the plan table when choosing how many internal users you need.
What if none of these match what I do?
Work backward from the output and trigger. If the job starts with HTML, a public URL, or structured data that fills a template, the generation pages show the available input and output paths in more detail.
Start generating documents
in minutes
Sign up, build something real, and move to a paid plan only when you need more capacity.
No credit card required.