Alright. Awesome, folks. So today, we have a solution, that will help you get rid of lots of your data input, data manual data entry. If you have a use case that, you have some certain information, certain properties that needs to be exactly same on various associated records. So this, solution will help you automate that.

I call it a cross object data flow solution. That's a made up name, but that's what I call it. The idea is to when we have a origination contact, a primary contact, you can say, the first contact and a company associated to that. So we push the information from contact to company, for the first time.

When that happens, every time a new associated contact is created for the company, we can have the same same information to be pushed to those contacts. So for example, if a company is segmenting their contacts and companies in various types, like vendors, contractors, partners, prospects, and customers. So they're segmenting it like this. And a new contact arrives in your CRM, and that is a partner.

So a contact in a company is created for that. So what we are gonna do is we are gonna mark the partner on the on one property, either contact or company, whatever life fits best. Naturally, it will be on the contact record because that's been created, via a form or something. Then we will push that information, to the primary associated company.

And every time now a new contact is created via HubSpot, sales extension, email extensions. So new contacts are getting added. So you don't have to populate that, type property again and again. So that's that's the whole idea.

But this can work in various different use cases. Like, for example, country, region, billing address, or any unique identifier that needs to be same across your across your objects and across all the associated contact with the company that that needs to be unique in your system. Maybe if you wanna use that information for, personalization, or any kinds of email marketing or for your back end CRM stuff. So that can be taken care of.

So let's look at the workflows. So this one.

So, basically, we just check the contact type is known and the primary associated company is known, and the primary associated company does not have any, type known, right now. So then we push the contact type to the company type. Simple.

Then once we have this information populated on the company, what we're gonna do is every time a new contact is populate, created in the system and we just need to populate that same information, we can have that. And you can see there is a decision box here. So, for example, you have certain exceptions if if in case you have certain ex exceptions like, the company's partner, but you have a person who is also a contractor, or or something like that, and it needs to have different data, you you can have that using if then branches. You can give your reps some time.

I've just added a minute for testing. You can give them one day or a week or a few hours based on your business. And then they can either have a task to just check if that populate, populate property is correct. Or if it's empty, then system's gonna assume that it needs to be auto populated with the automation, and it's gonna push from the company to contact.

One more automation I have is for your historical records. So so for example, if you wanna sync all the information, from company to all the associated record, then you can just do it. Just remember to have that specific property as a retrigger and just, enable that retriggering using the just empty that field and select the type again, and it's gonna populate again. So this is how it's gonna work. Hope this is helpful for you a little bit. If you have any further questions on this, I'll be happy to help.

Until next time. See you.