Calling/Extracting/Mapping fields from Custom Objects (and Zoom)?

[Anonymous]

Hi,

We are using Zoom as our webinar platform and want the user registration details to be automatically imported into Marketo. This is currently done via webhook and is working properly for the standard form fields: name, email, phone etc.

However, for a "custom question" in Zoom, both the question and the answer are stored as the field value. The Marketo custom object field value looks like this: [{"Qs":"Organization Type","Ans":"Health Plan"}]

In the example case above, I want to map only the answer "Health Plan" to an existing Marketo field "Organization Type".

If it's not possible to extract just the answer portion, I could still do something like a trigger campaign to set the value with an "If" condition on a Change Data Value action. (if field contains "Health Plan", change data value of Organization Type to "Health Plan")

How is it possible to work with a custom object field value?

[SanfordWhiteman]

If it's not possible to extract just the answer portion, I could still do something like a trigger campaign to set the value with an "If" condition on a Change Data Value action. (if field contains "Health Plan", change data value of Organization Type to "Health Plan")

You can't manipulate the values of Custom Object fields in Flows (that's what it seems like you're asking).

The closest you could get to this is using Velocity + Send Alert + Webhook to write the Ans value back to a a flat string field on the Person. Not something to do without a developer (though relatively easy once you have one and the requisite services).

[Anonymous]

Thanks for your reply.

What I was suggesting with the workaround is to make an operational campaign that sets the field value, like so:

Smart List

If Person Has [custom object id] = true

with constraint: [field name] is [{"Qs":"Organization Type","Ans":"Health Plan"}]

Flow

Change Data Value [Organization Type] = Health Plan

That seems like it would work to solve this issue. It essentially extracts the "Health Plan" part of the field value and assigns it to the correct place.

[SanfordWhiteman]

You're not extracting it -- you're creating a static flow step that covers a single known value.

In quantity, or with unknown input, that's not maintainable, but obviously for a one-off it's fine.

[Anonymous]

Good point, and I agree it doesn't scale well.