When building a flow that has a chain of multiple lookups or imports, some of the secondary lookups or imports in the chain might rely on data retrieved earlier in the flow.
Responses returned from an application's server for a lookup or an import may impact the behavior of subsequent lookups and imports. Response mapping allows you to define the actions integrator.io takes according to responses returned by the server when making a request to an application.
For example, if a request has been made for a certain value in a specific field, and the value exists, that should trigger an import of the data in the subsequent lookup or import. If the value doesn’t exist for a given record, you can define a specific action to be taken (like clearing the data record in the import application).