Use this pattern when a new form submission or app event needs a record and a team notification. Configure it with the gadgets and test accounts installed in your deployment.

​
Sequence

  1. Receive the event and load a representative sample.
  2. Find the event’s stable identifier in the destination table or app.
  3. Create or update the record according to the duplicate rule.
  4. Prepare a short message with the record identifier and the next action.
  5. Send it to the intended test channel or mailbox.

​
Check the result

Submit two samples with different IDs, then repeat the first ID. Confirm the records and messages follow your chosen duplicate rule. Inspect the run history and verify the target channel and account. Before live use, publish the reviewed configuration, enable the actual trigger and inspect its first invocation.