This article is intended to help teach you how to troubleshoot these types of issues, but it will not cover any explicit issues in external systems.
Where to Look
There are a variety of reasons that data might not be transferring to or from iPaaS.com. Since iPaaS.com has robust error logging capabilities, any issues with data not transferring that is not in the logs is likely due to settings in iPaaS.com, the external application and/or how the webhooks are configured.
If there is not an error, the data is not in the destination system, and the hook came over, then iPaaS.com made a determination not to transfer the record.
Questions to Ask
Is there an external ID for the record?
Checking if there is an external for the record for the system in question is a good way to check
Are mappings (and more importantly filters with exclusions) configured based on the desired outcome?
Are webhooks/polling enabled based on the desired outcome?
Common Issues
Webhook is not Being Sent / Received
Ensure the webhook for that data is turned on in the settings for the application.
Test in Postman if the webhook is being sent.
Mapping is not Created
iPaaS.com mappings provide a location for the data to go. Review the mappings for the subscription to ensure the data is set to go to the right place in iPaaS.com or in the external system.
Mapping Filter is Excluding the Data
iPaaS.com mappings allow data to be filtered out if needed. Reviewing the filters to ensure that the record in question would pass through is key to ruling out this as a possibility about why data did not transition correctly.
No External ID Present
Anytime iPaaS.com communicates with an external system and retrieves, creates or updates a record in that system it will log the external ID in iPaaS.com.
If an external ID is not present on the record in iPaaS.com then the record is not in the external system.
To resolve this, run a manual sync.