Javascript address importing issue

Hi ​@Ander05 

You do not need to start fresh each time. Duplicating the Zap is fine.

The old address is usually just cached test/sample data in Zapier — not what the live Zap will use after publishing.

To clear it:

1. Open the Trigger step
2. Click Test Trigger → Find New Records
3. Select a NEW customer/job record
4. Re-test the Code step

Also make sure your JavaScript uses dynamic fields like:

const address = inputData.address;

and not hardcoded addresses.

If needed, re-map the fields in the Code step after duplicating the Zap.
If you're still running into issues after trying these steps, feel free to drop a screenshot of the error and a quick description of what your Zap is doing—happy to take a look and help troubleshoot.
 

Thank you Fahad! 

I clicked on a new job record and verified the inputData:address is correct. I went through the process, but it still grabbed the old address: 1009 instead of the 45260. Any help would be greatly appreciated! 

Thank you!  

Hy ​@Ander05 

The screenshot shows the issue clearly: your Configure tab is still using the old mapped sample value: 

1. Contact Mailing Address: 1009 North Park...
Even though your Test tab shows 45260, the input field itself never refreshed after duplicating the Zap.

Fix:

• In the mailing_address field, click the X to remove the old mapping
• Re-select Contact Mailing Address from the new trigger sample
• Test again

Your JavaScript is fine. The stale mapping is the problem.

Thank you! Is there anything that I need to do before publishing this zap to make sure the old mapping does not stay? Thanks 

Hi there ​@Ander05 👋 When the Zap runs live, whatever address value is in the selected address field will be passed to the Code action so you should be all set!

But if you want to double-check before publishing the Zap you can always select a different test record that has a different address, then just retest the Code action to make sure it outputs the right address.

Hi Ander05,

Before publishing the duplicated Zap, I would do one clean remap pass so the live Zap cannot keep pointing at old sample values.

My checklist:

1. refresh the trigger with a new AccuLynx job/customer record,
2. remove and re-add every mapped address field in the Code step input panel,
3. confirm the Code step uses `inputData` only and has no hardcoded address fallback,
4. run the Code step with the new sample and check the output,
5. publish only after one live test record writes the correct Handwrytten address.

The key is that the JavaScript can be correct while the Zap editor input mapping is stale. A redacted screenshot of the Code step input fields plus one test output is enough to confirm the publish checklist.