Moves an existing HTML presentation, created by the sales team with the design system, customer branding, maps, and custom graphics, to a published Webflow link without a manual deployment or CMS handoff.
Sales needs more than a generic deck. The team assembles a customer-specific HTML presentation from approved design-system components, customer branding, maps, and custom graphics. Cloud Scale Deploy then removes the repetitive hosting and CMS work without flattening or rebuilding the approved artifact.
Sales authors the branded HTML artifact; one deployment command then coordinates the existing presentation, Vercel API, Webflow CMS API, duplicate check, iframe write, site publication, and returned link.
The sales team combines the approved design system, customer branding, maps, custom graphics, and account-specific narrative into a reviewed HTML presentation.
Run /deploy/presentation with the existing approved presentation and intended Webflow page name.
Send the presentation to Vercel through the API and capture the resulting hosted URL.
Use the Vercel URL as the iframe source and call the Webflow API for the managed presentation collection.
Check the proposed page name against the existing CMS to prevent a duplicate name, then paste the Vercel URL into the iframe embed field.
Publish the Webflow site, verify the managed page, and return the final link to the caller.
Authoring uses approved brand and design-system inputs; publishing is a narrow, repeatable deployment path.
/deploy/presentationOutput
A customer-branded HTML presentation with maps and custom graphics, its Vercel-hosted artifact, a managed Webflow page with the iframe field populated, and the published Webflow link returned to the caller.
Review
The sales narrative, customer-brand fit, map and graphic choices, final presentation approval, intended page name, and decision that the existing presentation is ready to publish.
The generated diagram shows representative authoring inputs, the command, two API boundaries, duplicate-name check, iframe CMS write, site publish, and returned link without exposing credentials, tokens, internal identifiers, or private client content. Sales authors and approves the artifact; the deployment path does not invent customer claims, overwrite a duplicate CMS page, or report success before the managed Webflow page is published.