Skip to main content

Bulk test orders

This workflow fills a test environment with random orders, so you have data to demo, test and train with. It is a tool for the colleague who sets up a test environment, not for daily sales work.

Test environments only

The workflow creates real orders. Run it only against a test environment, never against the environment your customers use.

In short
Where you use itIn n8n. Nothing shows on a page in Propeller
StartsBy hand, with Execute workflow
Changes in PropellerCreates up to 100 orders per run
Uses AINo
Runs in n8nOne per start
DifficultyMedium. You point it at your test environment and confirm that in a setting

What you get​

Up to 100 orders, each for a random contact with 1 to 10 random products from your own catalogue, in random quantities. Each order gets one of three statuses at random: NEW, CONFIRMED or VALIDATED. The orders show in the order lists of the Sales Hub and the Backoffice.

The Orders list in the Backoffice on All, with the three test orders of one line each at the top

What you need​

  • An n8n account with the credential Propeller API key, holding a key of your test environment. See Set up n8n and connect it to Propeller.
  • An API key with Viewer access on User management and Product Data and Owner access on Order Data.
  • A look at Shops & Channels > Event Actions in the test environment. The workflow sends no email itself. If an event action reacts to the trigger ORDER_CREATED or ORDER_UPDATED, the contacts on the orders do get that email. Switch such an action off first. See Event Actions.

How it works​

The workflow picks random contacts and products. It keeps the contacts whose company has both a delivery and an invoice address. Of the products it keeps the ones that have a price. Then it creates the orders in the same way the webshop does, in groups of 10.

Good to know

The workflows and agents in the Agent Hub are free to use and adapt. They are examples, not supported product features. Test them in a test environment and check the results before you use them on real customers.

Install it​

Install a workflow from the library explains each step.

  1. Import the file into n8n.
  2. Check that the eight nodes that talk to Propeller use the credential with the key of your test environment.
  3. Open the Settings node and set API_URL to the address of your test environment.
  4. Set I_CONFIRM_TEST_ENVIRONMENT to true. Until you do, the workflow stops with a message and creates nothing.
  5. Click Execute workflow.

After the run the orders are in the order lists. There is nothing to publish: the workflow only runs when you start it.

Make it yours​

SettingDefaultWhat it does
ORDER_COUNT100The number of orders to create
PRODUCTS_PER_ORDER[1, 10]The lowest and highest number of products on an order
QUANTITY[1, 5]The lowest and highest quantity on a line
STATUSESNEW, CONFIRMED, VALIDATEDEach order gets one of these at random. See Fill in order status codes
CHANNEL_ID1The channel the orders are created in. The number is in the Id column under Shops & Channels > Channels
SOURCE'Webshop'The source that is stored with each order

Limits​

  • The workflow has no undo. Orders it created stay until you delete them.
  • n8n stops a run after one hour.