I’m encountering issues with the Zapier integration for OpenPhone. The test recording URL is a placeholder, and actual call recordings and some contact details are missing. Anyone else facing this?
i had same issues w/ my zapier integration. sometimes its a glitch on openphone’s side, recordings and contacts arent always cert. hope they soon roll out a fix, otherwise u might want to contact support
After struggling with this integration some time ago, I found that my issues seemed related to temporary glitches on the backend. I noticed your concerns and had similar experiences where the data shuffled inconsistently. Through trial and error, I discovered that reconfiguring some integration settings and even briefly deactivating then reactivating the Zap sometimes helped restore proper data flow. Although it’s not a permanent solution, I opted to document the occurrences which eventually assisted support in identifying a longer-term fix. It improved overall integration stability over time.
I have observed similar discrepancies in the data retrieved through the Zapier integration. The placeholder recording URLs and incomplete contact details seem to be intermittent issues that may be linked to either synchronization lags or backend inconsistencies. When this happens, I found it helpful to verify that no recent changes were made to account settings and to review the integration logs for any error messages. Patience and periodic re-testing have sometimes been the only temporary solutions until a device update or system fix is released.
i encountered the same, looks like a recurring glitch on openphone’s end. try a full integration reset, might help shake things off until they sort the backend issues
I have been tracking a similar issue with my Zapier integration for OpenPhone, and the recurring discrepancies seem to stem from backend updates that alter data handling. I found that verifying my API credentials and ensuring the authorized scopes match the latest OpenPhone guidelines has reduced some errors in data transmission. Additionally, I recommend monitoring your integration logs for any unusual error messages which might point to a configuration oversight. While the situation remains less than ideal, these measures have helped mitigate the impact of incomplete data delivery over time.