Skip to main content

Adjust a workflow with an AI assistant

A workflow is stored as a file with plain text. An AI assistant such as ChatGPT or Claude can read that file, explain it and change it for you. So you do not have to understand every block to make an example your own.

The Churn risk alerts example from the library opened in n8n: a note that explains it and its blocks in a row, from the schedule to Create Ticket

Before you begin​

  • Try the settings first. Each library page lists what you can change under Make it yours, such as the schedule or a threshold. For those you do not need an assistant.
  • Never paste a password or an API key into an AI assistant. The downloads in the library hold none. A file you export from your own n8n can.
  • Test a changed workflow in a test environment first. That is a second Propeller environment without real customers. Ask Propeller if you do not have one.

Let the assistant explain the workflow​

Start here, also when you do not plan to change anything. It is a fast way to judge whether an example fits your process.

  1. Download the workflow file from its library page.
  2. Paste it into the assistant with this request.
Explain in plain language what this n8n workflow does, what data
it reads from the Propeller API and what it changes or creates.

Change the workflow​

  1. Paste the file into the assistant and say what you want changed. Ask for the whole file back.
Here is an n8n workflow in JSON. Change it so it also skips
companies with the tag KEY_ACCOUNT. Keep everything else the same
and return the full updated JSON.

  1. Save the JSON the assistant returned as a file whose name ends in .json.

  2. In n8n, create a new workflow. Click the three dots at the top right, choose Import from File and pick that file.

    The menu behind the three dots of a new workflow in n8n, with Import from File highlighted

  3. Connect your accounts again. A workflow file never holds them.

  4. Run it once by hand and check the result.

  5. Publish the new workflow and switch the old one off, so they do not both run.

For a workflow behind an agent, check the Production URL of the Webhook node after step 6. If it differs from the address under Admin > Agents, change the agent.

Rebuild an example in another tool​

The examples are made for n8n. In another tool, such as Make, Zapier or Power Automate, you have to build the workflow again. An assistant can describe how.

Here is an n8n workflow in JSON. I use Make instead of n8n.
Explain what this workflow does step by step, then describe how
to rebuild it in Make, including the modules to use and the
settings per module.

Check every step against the library page of the example afterwards. The assistant rebuilds the logic, and details can shift.