Overview
No. Lead Created Date is not a required field.
Leave it unmapped and REsimpli uses the time the lead arrives. Mapping it unnecessarily is a common cause of date errors — including the invalid-date and NaN style failures people hit after the 6.0 upgrade.
Steps
Step 1: Open the REsimpli action step in your Zap
Step 2: Find the Lead Created Date field
Step 3: Remove the mapping
Clear it, unless you have a specific reason to keep it.
Step 4: Leave your other required fields mapped
Only the date mapping is being removed here.
Step 5: Test with a new sample submission
Step 6: Confirm the result
Check the lead was created in REsimpli with the created date you expect.
When you would map it
Only when your workflow needs to preserve a date from the source system — for example importing historical leads that should keep their original date.
Even then, the value has to be valid and in the format the integration expects. If the source sends anything else, the step fails.
Important Notes
Unmapped is the normal, correct setup for most Zaps.
An unnecessary date mapping is a common cause of failure. If your Zap throws a date error, this is the first thing to clear.
You do not lose the created date by leaving it blank. REsimpli sets it to the moment the lead is pushed in.
Frequently asked questions
Do I lose the created date if I leave the field blank?
No. It is set to the time Zapier pushes the lead into REsimpli.
When would I map the date?
Only if your workflow specifically needs to preserve an external date, and you have a valid value in the expected format.
Why am I seeing a date-related error?
The source is probably passing an invalid or incompatible value. Remove the Lead Created Date mapping and test again.
Troubleshooting
A date error on the REsimpli step
Clear the date mapping.
Re-test with a fresh sample record.
Confirm your other required fields are still mapped.
If it persists, note the exact error message before contacting support.