Open app

DocumentationWorkflowsTriggers

Anymize: Project created node

Starts the workflow as soon as a new project is created, optionally only once an instruction and/or memory is set too. Starts exactly once per project, as soon as all conditions are met. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Starts the workflow as soon as a new project is created, optionally only once an instruction and/or memory is set too. Starts exactly once per project, as soon as all conditions are met.

Use Anymize: Project created as a clearly defined step in an anymize workflow.

  • Starts a new workflow run.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Anymize: Project created from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Anymize: Project created has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
Only with project instructionOnly fire once the project has an instruction.Standard
Only with project memoryOnly fire once the project has a memory.Standard
Name containsOptional. Only projects whose name contains this text.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
project_idConfigure this value in the node panel.text
project_nameConfigure this value in the node panel.text
has_instructionConfigure this value in the node panel.boolean
has_memoryConfigure this value in the node panel.boolean

Example and test run

Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "project_id": "beispiel-projekt-id",
  "project_name": "Support Q3",
  "has_instruction": true,
  "has_memory": false
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles