The Connect Fields that Copper introduced are really interesting and we have found some good internal use cases. However, they really only serve as glorified navigation tools at this point.
I think to really unlock the potential of these fields, there are a number of other things that would need to happen to get the most out of them. Are there plans to do any of the following:
+3
While not super ideal, you can use the Webhook functionality in Zapier along with the Dev API endpoint for connect fields to make them work:
https://developer.copper.com/custom-fields/connect-fields/create-a-connection.html
That said, Zapier is beta testing something called “App Extensions” which will essentially allow you to create your own endpoint (e.g. Copper Connect Field):
https://help.zapier.com/hc/en-us/articles/16276574838925-App-Extensions-in-Zapier
All of this of course is a bit more advanced, so it depends on how technical you are.
Regarding your first 2 points though, curious as well 🤔
EDIT: (Figured I’d just share it here, this is what it’d look like (I’m pretty sure, haven’t fully tested it yet)
+7
Hi
For exporting connect fields - this is something that’s supported if you’re exporting directly out of Copper (as opposed to through our Google Sheets Add-on). Each connection direction exports as two columns: one for the name of the records it connects to, and one for the record IDs. So if I have a pair of People-to-People connect fields called “Manager of” and “Managed by,” my export sheet will have columns for Manager of people names, Manager of people ids, Managed by people names, and Managed by people ids.
For importing connect fields - we don’t currently have any timeline for that feature.
As for API access through Zapier, we don’t have any development planned for that in the near term. But
Hope that helps!
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.