Hi everyone! 👋 I'm working on integrating Attio CRM into n8n using the HTTP Request node and Attio’s v2 API. I’ve managed to create contacts via PUT /v2/objects/people/records, and that part seems to work fine.But I’m trying to understand if anyone has a solid setup or example workflow for things like: - Checking if a contact already exists (via email or LinkedIn URL) - Conditionally creating or updating based on that - Handling custom fields in the contact creation/update I’m currently using Bearer token auth, and also exploring the POST /v2/objects/people/records/query endpoint to search for contacts. Would love to see any working examples, workflows, or best practices from the community if you've done something similar. Thanks in advance! 🙏Also, if there’s an official integration planned or tutorial somewhere, I’d be happy to check it out!

Hey everyone! I’m trying to build a workflow in n8n that does the following: 1. Makes an API request to Lemlist to export leads in CSV format. 2. Converts the CSV to JSON. 3. Uploads the data to Google Sheets. 🔍 The issue I'm facing: - The HTTP Request node (using Lemlist API credentials) doesn’t allow me to change the Response Format to "File", so the CSV is returned as a plain string, not as a binary file. - Because of that, the Extract from File node throws an error, since it expects a binary input (data), but there’s none. - I tried parsing the CSV manually using a Function node, but it's becoming messy and unreliable with complex CSVs (commas inside values, quoted fields, etc.). ❓ What I’m looking for: - A solid method to parse the CSV string to JSON inside n8n without data issues. Any help or pointers would be massively appreciated! 🙏Thanks in advance.