Workflows

A workflow in TeleportHQ is a visual recipe that makes your web app do something, one trigger (like a button click or a form submission) followed by steps (like saving to a database, sending an email or opening a page), built without writing code; adding one makes a website a web app.

In TeleportHQ, open the Workflows panel in the editor's left sidebar, click Add Workflow, replace the starting trigger with the one you need, then add and set up each step on the workflow canvas; copy, paste and tidy steps from the canvas.

In TeleportHQ, select the button on the canvas, click On Click in the Workflows section at the top of the right panel, choose Create new workflow, then add the steps the click should run; More event types offers form, input and other browser events.

In a TeleportHQ workflow, every step can use the results of the trigger and earlier steps (the workflow Context), by dragging a value from the Context panel onto a field or picking it with the Select from context button.

In TeleportHQ, click a workflow step and click Test in the right panel (or right-click the step and choose Test this node…), fill in sample values for the data it needs, then click Run test to run that one step for real and see its output; the Test runs tab lists every test of the workflow.

In TeleportHQ, replace a workflow's trigger with Scheduled (Cron), pick a schedule such as Daily at 9 AM and a timezone, then publish your site; the workflow then runs on the server at those times with no visitor needed.

In TeleportHQ, replace a workflow's trigger with Webhook Received, copy its endpoint URL, publish your site, and paste the URL into the other service (for example Stripe, Zapier or Typeform) so its requests start the workflow on your server.

In a TeleportHQ workflow, add a Send Email step (SendGrid, Mailgun, Mailersend, Postmark or Resend) or a Send SMS step (Twilio, TextMagic, Infobip or SMSAPI), enter your provider's API key, then fill in the sender, recipient and message; the provider you set up becomes the project's provider.

In a TeleportHQ workflow, add a Data step (Create Item, Update Item, Delete Item, Select Data, Count Data or Raw SQL Query), choose the data source and table, then fill in the column values and filters, often from form data.

In a TeleportHQ workflow, open Add node → Integrations, pick an app such as Slack, Google Sheets, HubSpot or Stripe, paste your API key or token, then choose the Action and fill in its fields.

A list of every trigger that can start a TeleportHQ workflow and every step you can add to it, grouped by the categories in the Add Node menu, with one plain line explaining each.

In TeleportHQ, build a group of workflow steps once as a custom node in the Custom Nodes section of the Workflows panel, then add it to any workflow with the Custom Node step, so you change the logic in one place.

In TeleportHQ, open a workflow, click the AI Assistant tab in the right panel, pick a model (Auto, Fast or Smart) and describe what the workflow should do or what to change; the AI builds or edits the steps, shows roughly how many AI tokens each reply used with a Revert button, and asks you to connect any service a step still needs.

TeleportHQ shows a yellow "N issues" button at the top left of the editor when workflow steps still need keys, pages, elements or states (it opens the Issues window), a "N security issues" button when workflow code could leak secrets or run unsafe SQL (critical ones block publishing), and a "Not exported" badge on a workflow that can never run; each one leads you to the step to fix.

In a TeleportHQ web app, visitors' files are saved with the Upload File(s) workflow step, usually from a File Upload Field in a form, and stored in your project's Runtime Storage, which you can browse in the Assets Manager under Uploads.

When a TeleportHQ workflow doesn't run on your live site, it is usually not published yet, disabled or marked Not exported, uncovered by a web app slot, started by a trigger that doesn't currently fire (Data Triggers, A Custom Event is Triggered), or failing at a step; TeleportHQ keeps no log of past runs, so check with Test this node… and by looking at the result.

In a TeleportHQ web app, visitors subscribe to push notifications with a Subscribe to Push workflow step (usually behind a "Turn on notifications" button), you set push up once with Set up push notifications, and a Send Push Notification step sends a title, text and link to everyone subscribed, one signed-in user or one browser, even when your site is closed.

Yes; on a published TeleportHQ site, a page with a Page is Loaded, An Element Becomes Visible or Component is Loaded workflow, or a state filled from a data source, starts over each time a visitor arrives at it, even from the same page (another record, another address after the ?, another language), so those workflows run again; to run one only once per visit, let it remember in the visitor's browser that it ran.