Short answer: Click Use sample data instead of Test, or test with real static values, then map your fields and click Done without retesting.
Why it happens
While you build an integration, the trigger passes sample data, not a real item. Mapped fields hold placeholder values such as "Text data" or "SampleInstance001". These are not a real email address, record ID, instance ID or lookup value. Any action that needs a real record fails or returns nothing, even when the configuration is correct. You may see errors such as Text data could not be located, SampleInstance001 could not be located or invalid email: Text data.
How to fix it
- For process actions, click Use sample data instead of Test or Retest.
- Skip the retest and click Done to save the configuration.
If you need a real test, or real output to map in later steps (for example from Search an item, Fetch an item or Find records from a dataset):
- Replace the mapped field with a real static value for now. Use a valid email address, an existing record or dataform
_id, an instance ID, a known lookup value, a folder name or a sample JSON body. - Test the action.
- Map the dynamic field again.
- Click Done. Don't retest after mapping.
More tips:
- To get a real dataform ID for testing, add a text field with the formula
_idto the dataform and submit a record. The field captures the record's ID. - For Search an item after a Scheduler trigger, type a simple value (for example
a) in place of the scheduler output, then test. - When you map fields in later steps, pick them by their field IDs.
- For the HTTP connector, test with valid input values typed in, then map fields and click Done without retesting.
The same test-then-map pattern is described in the integration best practices.