In short: Remove records from Salesforce or any connected system safely with a Delete action node in Noca Flows, including record ID mapping.

Last updated:

Key takeaways

  • A Delete action node permanently removes records from an external system such as Salesforce in a Noca flow.
  • You can switch an existing node from Update to Delete inline in the Mapping section instead of adding a new node.
  • Delete requires a mapped Record ID, and optional Condition filters act as safeguards against accidental data loss.

Lesson: 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!

Frequently asked questions

How do I delete a Salesforce record with a Noca flow?

Add or open a Salesforce action node in Noca, and in the Mapping section set Select an Action to Delete. Map the mandatory Record ID field so the flow targets the exact record. The node label changes automatically, for example to Delete Contact. Optionally add Condition filters as a safeguard.

Can I change an Update node to a Delete node in Noca?

Yes. Click the existing node on the Noca canvas, open the Mapping section in the Properties panel and switch Select an Action from Update to Delete. The node label updates automatically, so you do not need to delete the block and add a new one. You then map the required Record ID.

How do I prevent accidental deletions in a Noca flow?

Use the Condition block below the mapping inputs of a Noca Delete action node. It lets you set rules that records must meet before deletion, for example requiring that a record's First Name or Last Name matches the trigger data. This protects production data against accidental loss.