A webpage is a specific type of HTTP route step designed to serve HTML content that can be opened and viewed directly in a web browser. Unlike API endpoints, which are designed for machine communication, Webpages are human-facing interfaces that allow you to display interactive content within your workflows.
Key features
Browser-friendly: Webpages output full HTTP responses containing HTML, ensuring they render correctly in any modern web browser.
Links page visibility: When you set your route type to "webpage," the endpoint is automatically added to your workflow’s links page. This makes it easy to locate and access, featuring:
A descriptive label and an earth icon for quick identification.
A rendered preview thumbnail so you know exactly what the page looks like before clicking.
Flexible templates: You can easily build interactive user interfaces using modern frameworks. Webpages often utilize templates like React + Tailwind, though you can use any template that outputs valid HTML.
Controlling access
You can manage who can access your content by configuring the route_auth setting. This allows you to restrict visibility based on your needs:
Space members: Restrict access to only members of the current space (default).
Tenant members: Allow access for any member within your tenant.
SSO: Enable access for external users via Single Sign-On.
Public: Make the content accessible to anyone on the internet (only use this when explicitly required).
Webpages vs. other route types
It is important to select the right route type for your specific goal:
Webpage: Use for human-readable HTML pages.
API: Use for machine-readable data endpoints (JSON).
Webhook: Use for receiving events from external services.
Other: Use for file downloads, redirects, or RSS feeds.