SOLVED

Sending an email to someone who doesn't already have a record.

Go to solution
LeaCharnley
Level 2

Sending an email to someone who doesn't already have a record.

We want to start issuing guarantees for our products via a more automated process. The data will be collected via a non-Marketo form on our website. In a lot of cases a copy of the guarantee email will need to be sent to a third-party who are unlikely to already have a record. I know I can get the data into Marketo via a custom object, but how do I then send the email to that third-party email address.

 

Thanks  

Lea Charnley
1 ACCEPTED SOLUTION

Accepted Solutions
Michael_Florin
Level 10

Re: Sending an email to someone who doesn't already have a record.

There are two mechanisms that can send emails to non-database people: Alerts and CCing. And as you said "copy of the email" that might be a viable path.

 

Email addresses in Custom Objects though can't be used for either, if I'm not mistaken. So you need to save that alertee email address somewhere on the person record - in this case in the field "Alertee_Email_Address".

 

Michael_Florin_0-1742404738296.png

 

View solution in original post

2 REPLIES 2
Michael_Florin
Level 10

Re: Sending an email to someone who doesn't already have a record.

There are two mechanisms that can send emails to non-database people: Alerts and CCing. And as you said "copy of the email" that might be a viable path.

 

Email addresses in Custom Objects though can't be used for either, if I'm not mistaken. So you need to save that alertee email address somewhere on the person record - in this case in the field "Alertee_Email_Address".

 

Michael_Florin_0-1742404738296.png

 

SanfordWhiteman
Level 10 - Community Moderator

Re: Sending an email to someone who doesn't already have a record.

Like Michael says, you can't send directly to an address stored in a Custom Object field using standard flows. (You can use a somewhat complicated set of API calls to send to such a value, but that's likely too much effort here as you haven't yet invested in a CO-based approach.)

I wonder, though, what the specific reason is that you don't want to create these people in your instance. Are the emails to them not intended to be tracked/audited?