Help Needed with Encoding Issues from Claygent

Hi Clay S., I'm having encoding issues from the claygent. I don't know why it is happening sometimes in encodes twice the name, which makes it hard later to decode it into a regular UTF-8 format. Can you help? Take care !

4 comments

Clay
APP
·
·
For encoding issues, ensure you're using UTF-8 encoded files with comma-separated values for the most reliable results. Our Encode URI Components integration can help encode text safely for URLs by converting special characters to their percent-encoded equivalents. If you're still experiencing double-encoding issues with Claygent, try uploading your data to a public Google Sheet, then download it again as a CSV and attempt the upload once more to address potential formatting problems. Could you share a specific example of the double-encoded names you're seeing so we can better understand the exact encoding pattern?
Source: Encode URI Components with Clay
Matthieu J.
·
·
That data come from a hubspot via a clay webhook how can I ensure the encoding ?
Clay
APP
·
·
For HubSpot webhook data, ensure proper payload validation and structure using JSON format. Use our Encode URI Components integration to safely encode text by converting special characters to their percent-encoded equivalents, which prevents double-encoding issues. Monitor and log webhook activity to debug encoding issues and track payload structure. Could you copy and paste the specific JSON payload or double-encoded names you're seeing so I can help troubleshoot the exact encoding pattern?
Sources: What is Webhooks? | Clay Encode URI Components with Clay
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

Help Needed with Encoding Issues from Claygent | Clay