Setup guide
Everything needed to install, configure, use and remove Turbyn. No account required to read this page.
Requirements
Section titled “Requirements”- A HubSpot account with Professional or Enterprise on at least one hub. This is what provides the workflow tool.
- Permission to install apps in that portal (a Super Admin, or a user with app-install permission).
- Data Hub is not required. App-provided workflow actions aren’t gated by it.
Install
Section titled “Install”- Start the install from Turbyn (Portals → Connect portal) or from the app listing.
- HubSpot shows you the permissions being requested. Review and click Connect app.
- You’re returned to Turbyn, and the portal shows as Connected.
Permissions requested
Section titled “Permissions requested”| Scope | Why |
|---|---|
automation |
Register the Run Code action so it appears in your workflow editor |
oauth |
Maintain the connection and refresh tokens |
crm.objects.*.read |
Let your code read the records it processes |
crm.objects.*.write |
Let your code update records |
Read and write scopes are what make your code useful. Without them ctx.hubspot can’t do anything. Grant only the object types you intend to work with.
Configure the action
Section titled “Configure the action”The action is available immediately after install; there’s nothing to configure at the portal level.
Per workflow step:
- Open a workflow and add an action.
- Choose Run Code under the Turbyn section.
- Saved action. Pick from your published actions (searchable).
- Field 1–5. Map CRM properties, earlier step outputs, or static values.
- Payload (JSON). Optional structured input.
Only published actions appear in the dropdown. If yours is missing, publish it in Turbyn first.
Outputs
Section titled “Outputs”output1–output5, json, errorCode and errorMessage become available to later steps. Copy them to properties, or branch on them.
Managing users
Section titled “Managing users”Turbyn workspaces are separate from HubSpot users. Invite colleagues from Settings → Members. Anyone in the workspace can see connected portals, actions and run history, including logged output.
A single workspace can connect several portals, which is the usual arrangement for agencies.
Disconnect a portal
Section titled “Disconnect a portal”Portals → the portal → Disconnect.
What happens:
- The connection and its stored tokens are deleted.
- Workflow steps referencing your actions stop executing and report an error.
- In-flight runs are parked rather than dropped. Reconnect within HubSpot’s pause window. Roughly a week, and they resume.
- Actions, versions and run history are retained, so reconnecting restores service without rebuilding anything.
Uninstall from HubSpot
Section titled “Uninstall from HubSpot”In HubSpot: Settings → Integrations → Connected Apps → Turbyn → Uninstall.
What happens:
- The Run Code action disappears from the workflow editor.
- Existing workflow steps referencing it fail rather than being removed. HubSpot leaves the steps in place. Remove them from affected workflows.
- Turbyn detects the uninstall and marks the portal disconnected. HubSpot sends no uninstall webhook, so this can take up to a day, or happens immediately if you press Check status in Turbyn.
Uninstalling in HubSpot doesn’t delete your Turbyn workspace. To remove your data entirely, close the workspace in Settings → Workspace → Close workspace. That deletes actions, versions, run history and stored secrets.
What happens to your data
Section titled “What happens to your data”- OAuth tokens. Encrypted at rest, refreshed server-side, never sent to the browser, deleted on disconnect.
- CRM data. Passes through a run; input and output payloads plus console output are retained for your plan’s history period so runs can be inspected and replayed, then deleted.
- Secrets. Encrypted at rest, decrypted only at invocation, never returned to the browser after saving.
- Your code. Stored so it can be executed. Not used for anything else.
Full detail in the privacy policy.
Troubleshooting
Section titled “Troubleshooting”The action isn’t in my workflow editor. Confirm the app is installed (HubSpot → Connected Apps) and look under the Turbyn section rather than among the native actions.
The dropdown is empty. You have no published actions. Drafts don’t appear.
Every run fails with ACTION_NOT_FOUND. The saved action was deleted or unpublished after the step was configured. See the error reference.
Runs never start. Check the portal is still Connected. If it shows a token error, reconnect it.