HTML actions
Use an HTML action to generate an HTML representation of the service’s review content for a later action or integration. It is useful where a downstream system needs structured rendered content rather than a PDF.
An HTML action does not create a new public web page. Treat its output as data for a controlled downstream use, and decide who will receive it and how it will be handled before configuring the action.
Choose the output mode
The action offers two output shapes:
| Output mode | Use it when | Includes |
|---|---|---|
| Full document | the recipient needs the complete rendered document context | outer document structure and associated presentation material |
| Main content only | a downstream system needs the lightweight review-content fragment | the main review content without the full outer document |
Choose the smallest output that meets the integration’s need. A lightweight fragment is often easier to send or embed; a full document is useful only when the consumer expects complete rendered-document context.
flowchart LR
A[Review content ready] --> B[HTML action]
B --> C{Output mode}
C -- Full document --> D[Complete rendered document]
C -- Main content only --> E[Lightweight content fragment]
D --> F[Controlled downstream use]
E --> FConfigure and use the output
- Add an HTML action from Page actions.
- Set a stable Action ID and name that describe the output consumer.
- Choose the trigger after the review content and values are ready.
- Select the full-document or main-content-only mode.
- Place the later action that consumes the output after this action.
- Test the full downstream hand-off in QA.
If the generated HTML is sent to another system, agree how that system will handle styles, scripts, links and user-entered text. Do not assume that HTML which looks correct in one context will be safe or readable in another.
Review the content, not just the response
Test a normal route, optional answers omitted, long free text and every conditional section. Inspect the generated output in the same way the receiving system will use it. A successful action response only proves that content was generated; it does not prove the consumer renders it safely or correctly.
Use clean review-page content: meaningful headings, clear labels and no instructions that are relevant only while completing the service. This produces more useful HTML for documents, emails or integrations.
Avoid including sensitive values unless the downstream use has been approved. The HTML can contain the same personal information as the review content, so its retention and access rules must be considered alongside the receiving system.