Course Content
Flows – Intermediate
0/5
Configuring an Update Action – AI Agent
00:00
Configuring a Delete Action – AI Agent
00:00
Using Variables – AI Agent
00:00
Conditions – Simple Conditions – AI Agent
00:00
Course Exercise: Creating a Monday account based on Conditional Logic – AI Agent
00:00
Flows – Intermediate

Lesson Guide: Configuring a Delete Action Node

Now that you know how to read, create, and update records, let’s look at how to permanently remove data from an external system. This guide walks you through setting up a “Delete” action, updating your node parameters inline, and configuring advanced safeguards to protect your production data against accidental loss.

Step 1: Open Your Existing Node Parameters

  • Open your flow builder canvas (e.g., Test Academy Video 3).

  • Instead of deleting your current block and hunting for a brand new one, click directly on your existing on-canvas node (such as your previous Update Contact block).

  • This will instantly open its configuration fields inside the Properties panel on the right side of the screen.

Step 2: Swap the Operation Type Inline

  • Inside the right-hand sidebar, open the Mapping section dropdown.

  • Navigate down to Step 3: Select an Action.

  • Click the dropdown list and switch the setting from Update to Delete. Notice that the node label on your canvas grid dynamically switches to 2. Delete Contact automatically.

Step 3: Map the Required Record ID Variable

  • Scroll down further inside the Mapping sidebar.

  • Locate the mandatory parameter field: Record ID. Just like the update function, your integrated application (e.g., Salesforce) requires this explicit system token to ensure your workflow targets and purges the exact file intended.

Step 4: Configure Advanced Condition Filters (Optional Safeguard)

  • Look directly beneath your mapping inputs to locate the Condition block.

  • To ensure data safety before any execution runs, you can set custom rules to filter your records. For instance, you can define parameters specifying that a record’s First Name or Last Name field must perfectly match your trigger payload data criteria before the system is allowed to wipe the file.

💡 Congratulations! You have officially mastered all four core database operations inside Noca AI: Read, Create, Update, and Delete.

Now that you have a firm handle on structuring your backend action nodes, you’re ready to bring them to life. Join us in our next training module, where we will dive deep into Variable Data Mapping to learn how to seamlessly feed payload variables between your steps!

Previous
Next