Webflow · Arazzo Workflow

Webflow Deploy Custom Code to a Site

Version 1.0.0

Resolve a site, register a hosted script, then apply it to the site's header.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CMSE-CommerceNo-CodeWeb DevelopmentArazzoWorkflows

Provider

webflow

Workflows

deploy-site-custom-code
Register a hosted script and apply it to a site's header.
Lists sites, registers an externally hosted script for the chosen site, and applies the registered script to the site header by id and version.
3 steps inputs: displayName, hostedLocation, siteId, version outputs: appliedScripts, scriptId, siteId
1
listSites
List accessible sites to resolve a target site id.
2
registerScript
Register an externally hosted script against the site so it can later be applied. Returns HTTP 201 on creation.
3
applyScript
Apply the registered script to the site, placing it in the header by referencing the registered script id and version.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Webflow Deploy Custom Code to a Site
  summary: Resolve a site, register a hosted script, then apply it to the site's header.
  description: >-
    A custom-code deployment flow. It resolves the target site, registers an
    externally hosted script against the site so it becomes available, and then
    applies that registered script to the site by referencing its id and
    version in the header. Every step spells out its request inline so the flow
    can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
sourceDescriptions:
- name: customCodeApi
  url: ../openapi/webflow-custom-code-api-openapi.yml
  type: openapi
- name: sitesApi
  url: ../openapi/webflow-sites-api-openapi.yml
  type: openapi
workflows:
- workflowId: deploy-site-custom-code
  summary: Register a hosted script and apply it to a site's header.
  description: >-
    Lists sites, registers an externally hosted script for the chosen site, and
    applies the registered script to the site header by id and version.
  inputs:
    type: object
    required:
    - displayName
    - version
    - hostedLocation
    properties:
      siteId:
        type: string
        description: Optional site id; when omitted the first accessible site is used.
      displayName:
        type: string
        description: A human-readable name for the registered script.
      version:
        type: string
        description: Semantic Version (SemVer) string for the script (e.g. 1.0.0).
      hostedLocation:
        type: string
        description: The externally hosted URL of the script to register.
  steps:
  - stepId: listSites
    description: List accessible sites to resolve a target site id.
    operationId: list-sites
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      firstSiteId: $response.body#/sites/0/id
  - stepId: registerScript
    description: >-
      Register an externally hosted script against the site so it can later be
      applied. Returns HTTP 201 on creation.
    operationId: post-hosted-script
    parameters:
    - name: site_id
      in: path
      value: $steps.listSites.outputs.firstSiteId
    requestBody:
      contentType: application/json
      payload:
        displayName: $inputs.displayName
        version: $inputs.version
        hostedLocation: $inputs.hostedLocation
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      scriptId: $response.body#/id
      scriptVersion: $response.body#/version
  - stepId: applyScript
    description: >-
      Apply the registered script to the site, placing it in the header by
      referencing the registered script id and version.
    operationId: add-custom-code-tosite
    parameters:
    - name: site_id
      in: path
      value: $steps.listSites.outputs.firstSiteId
    requestBody:
      contentType: application/json
      payload:
        scripts:
        - id: $steps.registerScript.outputs.scriptId
          version: $steps.registerScript.outputs.scriptVersion
          location: header
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      scripts: $response.body#/scripts
  outputs:
    siteId: $steps.listSites.outputs.firstSiteId
    scriptId: $steps.registerScript.outputs.scriptId
    appliedScripts: $steps.applyScript.outputs.scripts

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/webflow-deploy-site-custom-code-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.