Some services are on paid plans. They are marked with a diamond wherever they appear. On the Free plan you can still add them and build and test the steps that use them; the plan matters when a workflow that uses one is published and runs on its own.

Who can do this

Workspace Admins and Editors add connections and build workflows. Only the company Owner changes the plan.

Premium connections are included in the Starter, Pro and Enterprise plans. Today the premium services you can connect are HubSpot and Microsoft SQL.

Steps

  1. On Connections, select + Add connection. Premium services show the diamond, and on Free their hint ends in "· Paid plans".
  2. Select the service. On Free a note says, for example, "HubSpot is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
  3. Add the connection as usual and select Save connection.
  4. In the designer, add the step and choose the connection. The step can be set up and run as a test.
  5. Select Publish. On Free, publishing stops with "“Create, update or find a record” needs a paid plan. Change the plan, or remove it and publish the rest." With several, "2 steps need a paid plan. Change the plan, or remove them and publish the rest."
  6. To publish it, the company Owner changes the plan. Otherwise, remove the step and publish the rest.

What happens next

  • After the plan changes, publishing works and the workflow runs as usual.
  • If the plan later moves back to Free, live runs of a workflow with a premium step are skipped: "“Create, update or find a record” needs a paid plan, so the run was skipped. Once the plan changes, the workflow runs again from its next trigger." Test runs still work.
  • A run that was waiting (on a Wait step, say) when the plan changed stops: "The plan changed while this run was waiting: … needs a paid plan, so the run stopped before going on."

Good to know

  • On Free, the Connections page says: "Connectors marked with a diamond are on paid plans. Add one and test the steps that use it on any plan; publishing a workflow that uses it asks for a paid plan."
  • Hover over the diamond to read "Paid plans — test on any plan, publish on a paid one".
  • Your own keys for OpenAI, Anthropic and Google Gemini, Microsoft 365, Google Workspace, PostgreSQL and API keys for HTTP Request are on every plan.

If something goes wrong

What you see Why What to do
"“…” needs a paid plan. Change the plan, or remove it and publish the rest." A step uses a premium connection on Free. Ask the company Owner to change the plan, or remove the step.
Runs show Skipped with "… needs a paid plan, so the run was skipped." The plan no longer includes premium connections. Change the plan; the workflow runs again from its next trigger.