I have a client with HubDB data in one portal who want to synchronize that HubDB data with contacts in a different portal. What's the best way to do this?
More details:
Portal A has a HubDB table the includes an email address. Whenever a new row gets aded to the table in Portal A, we would like to use the email address from that row to create a contact in Portal B.
Unfortunately, no. As the values stored in a HubDB table are not something that can be referenced via a Workflow, this is something that would have to be handled via the API as this will give you full control over the value pushed to the Contact Record.
With this API, you'll be able to interact with the data from one of your tables and have it updated and pushed to the new table. An example process which you could adopt is to query the Table A for new rows using the following:
Thanks, but to clarify - we need to push the data from the Table in Portal A to a Contact in Portal B. So, the data is moving across portals. I understand this can happen using an script that calls the HubDB API to get data from Portal A and the Contacts API to push the data to Portal B.
Is there any way that I can kick this off from a workflow running in Portal B?
Unfortunately, no. As the values stored in a HubDB table are not something that can be referenced via a Workflow, this is something that would have to be handled via the API as this will give you full control over the value pushed to the Contact Record.