Discover, test and use website actions in workflows
Inspect the actions your website exposes, their input schemas and live availability, then choose an explicit action in the workflow builder.
In this article
Before you begin
Use a test environment and the smallest necessary access. Keep workspace API keys and signing secrets on your server, outside browser code and public screenshots.
Step by step
- 1
Install the host integration
Your website must load Corthex host-actions.js, register its own validated callbacks with CorthexActions.register, and load this assistant's standard widget. The widget or Knowledge alone does not create product, cart or account actions. Existing server commerce connectors have their own tools and transport.
- 2
Open and approve a test session
A workspace administrator opens the agent's Integrations → Website actions, enters the exact HTTPS page, then chooses Connect website. Approve the browser prompt on the website. This opens your own browser session; it never accesses another visitor's browser. A popup blocker, another bot ID or an old SDK can prevent the connection.
- 3
Inspect availability and input
The panel discovers every action page and shows names, descriptions, registered input fields and the full JSON schema. Available now means registered in the connected page/session. Saved definitions are explicitly unverified; absent saved actions are not available in the current session. Read-only annotations are declarations, not permission checks.
- 4
Run an explicit test
Choose an action, fill its fields or JSON input, then click Run action in test session. This executes a real action in that browser session and can change its data; use a test account/cart where appropriate. Native access checks and confirmation still apply. Review the raw result. Test input and results stay in the panel and are not saved to the discovery catalog.
- 5
Save definitions for the workflow builder
Save discovery stores only the current origin, path and bounded action definitions for this assistant. It replaces its previous saved discovery and uses a revision check to prevent stale overwrites. Refresh after page or sign-in changes. Closing, reloading or resetting the website session requires reconnecting; a saved list never authorizes execution.
- 6
Choose a Website action node
Open Workflows, assign the workflow to the correct assistant, then Add step → Website action. In its conversation builder, select the Website action node and choose a saved action. Fill literal inputs or bind collected answers with {{answer}} and previous results with {{result.field}}. Choose a result variable and connect Success, Unavailable, Cancelled and Error / unknown outcome to appropriate next steps. Complete all required node fields before publishing.
- 7
Simulate, publish and test on the website
The conversation flow test simulates the chosen outcome and never executes website actions. Publish deliberately, then test the intended trigger in a real standard embedded chat on the configured website. The server suspends the workflow, the browser executes the exact action, and the correlated result resumes the published revision. Other channels or unavailable actions use the Unavailable branch. An uncertain mutation is never automatically reissued.
Websiteacties instellen — Nederlands
Open je assistent → Integraties → Websiteacties. Verbind de juiste webpagina en keur de verbinding op de website goed. Je ziet daarna welke acties daar nu geregistreerd zijn, welke invoervelden verplicht zijn en welk JSON-schema geldt. Een opgeslagen ontdekking is alleen een bewerkreferentie, geen bewijs van actuele beschikbaarheid.
Een echte test voer je uit met Actie uitvoeren in testsessie. Die gebruikt jouw verbonden browsersessie en kan gegevens wijzigen. De normale websitecontroles en bevestigingen blijven gelden. Alleen definities worden opgeslagen; testinvoer en testresultaten worden niet in de ontdekking bewaard.
Sla de ontdekking op. Open Workflows, koppel de juiste assistent en kies Stap toevoegen → Websiteactie. Selecteer in de gespreksflow de actie, vul invoer of {{answer}}-variabelen in en verbind Gelukt, Niet beschikbaar, Geannuleerd en Fout. De flowtest simuleert alleen; test na publiceren ook de echte websitechat. Andere kanalen zonder browserverbinding volgen Niet beschikbaar.
Acties komen uit de website-integratie; de gewenste gespreksvolgorde komt uit je assistentinstructies of workflow. Knowledge bevat broninformatie. Tools van een server-winkelconnector staan apart in het overzicht en gebruiken hun eigen sessie en scopes.
Good to know
Knowledge provides reference information; assistant instructions guide model-selected tools. Explicit Website action nodes use the saved action name and origin, then the website's current implementation. Saved discovery is not a credential or executable code.
Commerce connector tools are listed separately with their input schemas, granted scopes, assistant setting and confirmation policy. Personal operations also need a verified visitor session. Browser inspector tests do not impersonate customers or invoke server connector tools.
Workflow result.status, result.summary and result.json can be used in later nodes. Small primitive result fields are also available. Results remain untrusted data; the server's existing tenant-scoped conversation cursor retains bounded fields to resume the workflow. A confirmation proposal is not treated as a completed change.
The inspector connects only the dashboard's own opened website window, the SDK's origin and the matching temporary nonce, after native approval. No shop cookies, API keys or account credentials are passed to the dashboard or saved catalog. Test results may contain personal data from your own session, so inspect only what you need.
Check the result
Check the response, relevant delivery history and organisation scope. Use the Public REST API reference in this Help Center for the technical contract.
Questions & troubleshooting
Why do I see saved actions but cannot run them?
A saved discovery is an editing reference. Connect a live website session and approve it on that page. If the action is absent there, navigate or sign in on the website and refresh. After a full reload or session reset, reconnect.
Why is the connection still waiting for website approval?
Allow the popup, use the exact final website URL, and open the dashboard on the same origin that serves its host-actions.js SDK. Check the correct assistant widget/current SDK are loaded, then approve the native browser prompt. Strict cross-origin opener policies on the host website can prevent this popup transport. Do not weaken the website's access rules; use a supported test page or adjust its integration deliberately.
Why did the workflow follow Error after a timeout?
A timeout or interrupted connection cannot establish whether a native change happened. Read the current website state before trying again. The server does not replay an issued workflow mutation automatically, and the SDK deduplicates the same command within its connection.
Can I use a connector tool as a browser website action?
These are different transports. Server commerce tools use their connector's native session/scopes. Website action nodes use callbacks registered in a standard embedded chat's current browser page. Inspect the source shown in the panel; do not copy a server tool name into a browser action and expect it to appear.
Rate this guide on this device. Ratings are not sent to Corthex.