Skip to main content
TradeVulcan logoTradeVulcan
Book a live walkthroughStart my 14-day trial
Menu
Build around your first revenue leak.

Choose a plan, add your workflows, and review the total before checkout.

DashboardBook a live walkthroughBuild my stack
All docs
Work Mode Guides
Vulcan Intelligence

Use Work Mode to create, edit and publish Site Spark forms

Create unpublished forms, refine supported text and style, reorder ordinary fields, and handle publishing as a separate reviewed action.

Vulcan Intelligence product illustration supporting the guide: Use Work Mode to create, edit and publish Site Spark forms
Product illustration. Examples do not establish that a plugin or action is enabled for your workspace.

Choose the exact form

Open the correct Site Spark deployment and form, or ask Work to list the permitted forms. Confirm the name and whether the selected version is live or unpublished. Work review supplies the current form, version and revision before a change.

A returned excerpt may not contain every field or the full saved text. For a detailed reorder or copy review, ask for the remaining items before approving a plan. Never treat a truncated field list as the complete form.

Create or duplicate a draft

  1. For a new form, ask Work to show the available templates and choose a suitable starting point.
  2. Name the form and target deployment. Review the proposal to create an unpublished draft.
  3. To make an independent copy, ask to duplicate the existing form. The original remains unchanged.
  4. To edit the live version of the same form, ask for an editable draft of that version. If a draft already exists, use it rather than creating a competing version.

Make a focused edit

TRY THIS PROMPT

Review the unpublished Generator Estimate form. Change the submit label to Request my estimate and make the success message say our office will confirm the next step. Keep consent, required fields and CRM mapping unchanged. Do not publish.

Supported edits include form-level copy, ordinary field labels/placeholders/help, a step’s title or description, selected visual styling and field order within one step. Each change uses the reviewed version and requires exact approval. Read the resulting form again after a save because its revision has changed.

Reordering requires every field in that step once, in the intended order. Consent, hidden content and other protected positions remain fixed. These controls do not add arbitrary fields, move fields between steps, change types or required flags, or rewrite routing. Use the form editor for work outside this supported scope.

Review the whole draft before publishing

Open the resulting draft and inspect its desktop and mobile layout, labels, errors and success message. Confirm what the existing routing and CRM settings do. A draft-copy operation does not validate live provider readiness.

When the complete draft is ready, explicitly ask to publish that exact version. Publishing is a separate approval, and the full draft—not only the last edited label—becomes public and accepts submissions with its existing settings. Check the public form afterward.

Archive without confusing it with deletion

An explicit archive request can prepare disabling the entire form on websites while keeping submissions, analytics and versions. Review its scope carefully. Archiving a form is not archiving a Site Spark deployment or deleting customer records.

For a stale-version conflict, reread and reprepare. For an interrupted approval, refresh saved status. Do not submit the same form creation again merely because the browser did not finish its response.

Continue learning