We've been testing Nos Agent for outreach automation and it's solid for prospecting, but I'm running into friction syncing qualified leads back into our Salesforce instance. The mapping seems straightforward but we're losing some custom field data in translation. Before I dig deeper into their docs, curious if others have solved this elegantly or if we should just accept some manual cleanup?
I haven't worked with Nos Agent specifically, but custom field loss during CRM sync usually points to field mapping configuration—have you checked if those fields are set as "exportable" in both systems, or if there's a field type mismatch (like text vs. picklist)? I'd suggest testing with just one custom field first to isolate the issue before assuming manual cleanup is necessary. What specific field types are getting dropped—text, dropdowns, or something more complex?
I'd check if Nos Agent supports custom field mapping through their API or webhooks rather than relying on native sync—sometimes bypassing the UI layer gives you more granular control. Have you documented which specific custom fields are dropping during the transfer? That detail might help you build a simple transformation layer or reach out to their support with concrete examples, since field-mapping friction is usually solvable once they see the exact data structure mismatch.