Append-only covered events
Covered audit events are append-only, so later activity does not rewrite an earlier event. Search, filter, and export the supported trail when investigating a workflow.
Operations
From approved records to
From approved records to
each document step
Automate internal reports, employee onboarding packets, logistics labels, and compliance documents directly from database records and business applications.
Free account, no credit card
Built for operations teams
Internal Reports
Map reviewed database or dashboard values into a PDF report on demand, on a schedule, or after an event.
Compliance Documents
Render approved reports, policies, and filing inputs with controlled templates, versions, access, and retention.
HR & Onboarding
Prefill approved offer, contract, benefit, and onboarding templates from the employee record.
Shipping & Logistics
Use validated logistics data in manifests, bills of lading, declarations, and delivery records.
Financial Statements
Place approved accounting values into statement and expense-report layouts for review and filing.
SLA & Status Reports
Render status and service reports from reviewed monitoring values and the reporting terms you supply.
How it works
1
Choose the source and trigger
Start with an ERP, HRIS, accounting, form, or other record exposed through a connector, webhook, schedule, or API.
2
Map and approve the template
Define the dates, names, figures, tables, fixed text, version labels, and conditions the document needs, then test edge cases.
3
Route, render, and reconcile
Complete any approval steps, submit the work, track each result, and route the file to its delivery and retention destination.
Make the approval route part of the record
A request may need different approvers based on amount, department, category, or other submitted values. Encode the policy as tested conditions and record each decision. Move the sample amount below to see how one example route changes.
Department
5 steps before it is issued
- 1 Requester Submits the form
- 2 Line manager Any spend at all
- 3 Department head Over $1,000
- 4 Security review IT spend over a threshold
- 5 Purchase order issued The document is produced and filed
Set the amounts from your own policy. Name the approver roles, delegates, exception path, and policy version too. Test values below, on, and above each boundary before publishing the form.
Keep enough context to answer a later question
A later review may ask which source record, template, policy, approvals, and delivery event produced a file. Decide which evidence belongs in cloudlayer.io and which remains in the upstream business system. Do not treat the PDF itself as the complete audit record.
Link the source record
Carry stable record identifiers through the request and storage path. Your source system remains responsible for the meaning, validation, and history of the business values.
Configure retention as policy
Set retention, deletion, and legal-hold behavior according to the applicable plan or contract and your policy. Confirm which records and files each setting covers.
Separate access from activity
Roles describe what an internal user can access. Audit events describe supported actions that occurred. Review both rather than treating permission as proof that a person acted.
Record the template version
Keep the template version with the render or business record so a later review can identify the layout and fixed content used for that output.
Choose the right persistence mode
Secure and zero-retention modes cover workflows with stricter persistence needs. Verify their exact behavior and purge timing before building a requirement around them.
Map the manual handoffs before automating them
Rendering is one step in a longer process. Record where people rekey values, find the latest template, wait for approval, check a result, deliver the file, and reconcile completion. Those handoffs define the workflow worth improving.
- Rekeying values between systems. Manual transfer creates another place for values to diverge. Prefer stable field mapping, validate required inputs, and keep the upstream record as the source of truth.
- Repeated fixed content. Logos, registered addresses, period labels, and approved footers drift when copied across files. Put shared content in maintained templates or blocks and test the active version.
- Approval without visible state. Record who owns the next decision, when it was assigned, and what happens if that person is unavailable. A routing rule makes the waiting state inspectable.
- Logic owned by one local file. Document the mapping, conditions, and schedule outside a personal spreadsheet. Give the workflow an owner, test cases, and a recovery path before changing the existing process.
- Repeating a known report cycle. Monthly packs, weekly summaries, and quarterly reports can reuse approved templates and mappings. Scheduling removes the reminder, but reconciliation still proves the outputs ran.
Define what a complete document run means
A successful API response proves that work was accepted. It does not prove that every file rendered, passed review, reached its destination, or matched the business records expected for the period. Give the run its own checklist and identifiers so partial completion is a visible state rather than a missing file discovered later.
Start with an expected manifest
List each output before submission: report type, period, business-record id, template version, destination, and owner. A run expecting 12 reports is complete only after all 12 entries have a resolved status.
Keep business ids stable on retry
A retry should reuse the report, employee, shipment, or invoice identifier allocated by the source system. Rendering the same business record again should not create a second business event by accident.
Record each render result
Store the job id, output status, error state, and resulting asset reference against the manifest row. Success for 11 files and failure for 1 is a partial run that still needs an owner and next action.
Separate render from delivery
A file may render and then fail to reach storage or the next system. Track delivery as its own step, including the destination, attempts, final status, and any fallback route.
Reconcile webhooks with polling
Webhooks provide prompt status changes, while the Jobs API covers missed events and recovery. Periodically compare unresolved manifest rows with job status until the run reaches a terminal state or an operator takes over.
Close with evidence, not silence
Mark the run complete after expected outputs, review, and delivery have been checked. Record who accepted any exception so a later reviewer can distinguish an approved gap from a workflow that stopped unnoticed.
Run this reconciliation on a small sample first. Include a valid record, a rejected input, a render failure, and a delivery failure so the operator sees each state before month end.
The pack that goes out every month
A recurring pack needs more than a calendar trigger. Define its reporting period and data cutoff. List the expected files, review state, delivery destination, and failure owner. The sample below shows one run producing 12 reports.
- Track the run and every output. One run groups the 12 expected reports, but each file can still have its own result. Mark the run complete only after reconciling the full expected set.
- Handle both events and missed events. Consume success and failure webhooks. If your endpoint misses one, query job status and alert the person who owns the run rather than treating silence as success.
- Give each file an explicit destination. Route output to your application or supported own storage. Use a path based on the period, report type, and stable record identifier, then handle delivery failures.
- Reuse shared content across the pack. Keep headers, approved footer text, and reporting-period rules in shared blocks where the documents truly match. Test all 12 outputs after changing that source.
Compliance & Audit
Structured documents with traceable inputs
Governed paperwork needs approved fields, layout, version, access, and retention rules. cloudlayer.io renders the data and template you provide. Your policy owner decides whether the result meets the rules that apply to the document.
Carry a stable record id into the workflow and storage path. Include the version, department, classification, and reporting period when they matter. That context helps later retrieval without asking the renderer to become the source system.
When a rule changes, update and approve the affected templates. Test representative inputs. Then decide which future or historical outputs must be rendered again.
Document Versioning
Carry the business version, relevant dates, and template revision with the output and its source record.
Event-Driven Generation
A closed period, signed record, or schedule can start a run. Reconciliation proves which expected outputs completed.
Structured Data Sources
Map validated ERP, accounting, HRIS, form, or database values into named template fields and tables.
Retention & Archival
Return finished files or send them to supported own storage under the path and policy your records process requires.
Operations workflow examples
Monthly financial report
- The period-close event or schedule starts the reporting workflow.
- The workflow validates the period, values, chart inputs, and comparison data.
- cloudlayer.io renders the approved report template.
- The PDF moves through review, delivery, storage, and reconciliation.
Employee onboarding packet
- An approved employee record reaches the chosen onboarding state.
- The workflow maps validated fields into each required template.
- cloudlayer.io renders each PDF and returns its own result.
- The workflow applies signature, delivery, access, and retention steps per document.
Questions, answered
Can approval routing depend on what was submitted?
Yes. Conditions can route a submission by amount, department, answer, or other supplied values. Define the thresholds, approver roles, fallback behavior, and exceptions from your own policy, then test every branch before relying on it.
How do I know a scheduled run actually happened?
Store the run and job identifiers, handle success and failure events, and reconcile every expected output. If your webhook endpoint misses an event, query the Jobs API for status. Treat partial success as a state to investigate rather than assuming the whole pack passed or failed together.
What does the audit trail actually record?
Covered audit events are append-only and can be searched, filtered, and exported. They record supported actions and changes rather than every fact from every source system. Retention and deletion depend on your plan or contract. So does legal-hold behavior.
Do the people filling in forms count as users on our plan?
Public respondents are not internal workspace users. Plan limits on internal users apply to people working inside the account, such as form builders, template authors, approvers, and administrators. Check the plan table for the included limit.
How many documents can a scheduled run produce at once?
Published concurrency is 2 renders on the entry tier, 8 on Business, and 25 on Enterprise. Larger sets wait in the async queue and each finished document uses 1 render. Test representative render times and choose a plan that meets the required completion window.
Where do the finished documents go?
Return the file to your application or route it to supported S3, Google Cloud Storage, Azure, Cloudflare R2, Backblaze B2, or DigitalOcean Spaces storage. Supply the destination and path on the request and handle any delivery failure in the workflow.
How do I automate recurring operational reports?
Schedule a workflow that gathers and validates the reporting-period data, then submit it with the report template. Track the render and route the PDF through the required review, delivery, and retention steps.
Can I generate a whole onboarding packet at once?
Yes. Keep each document as its own approved template and map the relevant fields from one employee record. Track the result and signature or delivery state of each file separately.
Can documents include compliance formatting?
Templates can carry approved headers, disclosures, version labels, and other fixed content. Your compliance owner must still decide what is required, approve the template, and review changes.
How do I handle high volumes?
Use async jobs or batches, store their identifiers, consume completion events, and reconcile expected results. Size volume and concurrency from measured demand rather than holding one request open.
Test one operations workflow
from source record to retention
Choose one recurring report or packet and verify its data, approvals, templates, results, delivery, and reconciliation.
No credit card required.