Check What Input Is Sent to a Data Mapper from an OmniScript

While testing an OmniScript, I ran into a situation where I needed to confirm what input data was actually being sent to a Data Mapper. The UI shows the mapping, but that doesn’t always guarantee the exact value being passed at runtime.

Here’s a simple and reliable way to verify it using Action Debugger.

---

Scenario

• An OmniScript calls a Data Mapper (Extract Action)
• An input parameter (for example, Agent_Email) is passed from the OmniScript JSON
• That parameter is then used in an Extract Object filter (for example, filtering Contacts by Email)

I wanted to make sure:

• The parameter exists
• The value is populated correctly
• The Data Mapper receives the expected value

---

Step 1: Configure the Data Mapper Input

In the Data Mapper Extract Action inside the OmniScript:

• Set the Data Mapper Name
• Under Input Parameters, map the input like this:

Contact Information:Agent_Email 

This means:

• Agent_Email is expected to come from the OmniScript JSON
• The Data Mapper will receive it under DRParams

---

Step 2: Verify the OmniScript Input JSON

Open Manage Input/Output Type → Edit Input JSON.

Make sure the value is present:

{

  "Agent_Email": "user@example.com"

}

✅ This is important
If the value is missing or null here, the Data Mapper will not receive it—even if the mapping looks correct.

---

Step 3: Use Action Debugger (Most Important Step)

Now run the OmniScript in Preview mode and open Debug → Action Debugger.

1. Find the Data Mapper Extract Action
2. Expand Request Data
3. Look for the DRParams section

You should see something like:

"DRParams": {

  "Agent_Email": "user@example.com"

}

``

✅ This confirms:

• The OmniScript passed the value correctly
• The Data Mapper received the expected input
• Any issues after this point are inside the Data Mapper logic itself

---

Step 4: Confirm the Data Mapper Response

In the same Action Debugger entry, check the Response section.

If the input is correct, the response should contain the expected records (for example, matching Contact emails).

---

Key Takeaways

• Action Debugger is the source of truth for what is actually sent to a Data Mapper
• Always check Request Data → DRParams
• Do not rely only on UI mappings—runtime data can differ
• If the value is missing in DRParams, first check:
  • OmniScript Input JSON
  • Data Mapper input parameter mapping

---

Why This Helped Me

This approach saved time by:

• Quickly isolating whether the issue was in the OmniScript or the Data Mapper
• Avoiding unnecessary changes to filters and queries
• Making debugging more predictable and repeatable