Managing QuickFlo from a workflow

Most steps reach out to other systems. This small family of steps points the other way: it lets a workflow manage your own QuickFlo account — the connections, environment variables, logs, and run history you’d otherwise manage by hand in the app.

The step that started it all: rotating a password. If a service makes you change a credential every 90 days, you can build a workflow that does it on a schedule instead of you remembering to.

What each step does

Step	What it’s for
Update Connection	Change an existing connection’s settings — for example, rotate its password on a schedule while leaving the username alone.
Create Connection	Add a new connection from a workflow.
List Connections	Look up your connections by name or type. Returns names and types only — never the stored credentials.
Set Environment Variable	Set or update a value in one of your environments.
List Environment Variable Keys	See which variable names exist in an environment (names only, never the values).
Query Logs	Search your workflow and connection logs — handy for a workflow that watches for errors and alerts you.
Query Executions	Look up your run history by workflow, status, or time range.

Example: rotate a password every 90 days

1. A Schedule trigger fires every 90 days.
2. A step generates or fetches the new password.
3. Update Connection points at the connection and sets just its password field. Everything else on the connection stays exactly as it was.

Because you only fill in the field you want to change, the rest of the connection is left untouched — you don’t have to know or re-enter the username.

Switching a connection's login method

Update Connection changes values, not shape. You can rotate a form-auth connection’s password, but you can’t switch it from a password login to a magic-link login — that’s a different kind of change. To do that, recreate the connection.

Who’s allowed to build these steps

Changing a credential or an environment variable from a workflow is exactly as powerful as changing it by hand in the app — so it needs the same permission. To save a workflow that creates or updates a connection or sets an environment variable, you need Secrets Admin access. QuickFlo checks this the moment you save the workflow, not later — so a teammate without that access simply can’t build one of these steps into a workflow in the first place.

The read-only steps (List Connections, Query Logs, Query Executions, List Variable Keys) follow the same idea with the matching view permission.

Your secrets stay secret

These steps are careful with sensitive values in both directions:

• Nothing sensitive comes back out. Update and Create Connection return only the connection’s name, type, and id — never its config. List Connections returns names and types. List Variable Keys returns key names, never values. There is deliberately no step that reads a stored password or secret back out of a connection.
• Secrets never land in your run logs. When you set a password or a variable value, that value is stripped out of the workflow’s saved run record. So even someone who can read a run’s details can’t recover the secret you set.

Caution

One thing to know: these steps run with your workflow’s own access when the workflow runs. If a workflow that contains one of these steps is shared as a package and installed elsewhere, the installing account runs it. Only install packages you trust.