Closed leandrosardi closed 3 months ago
et = Mass::EnrichmentType.upsert({
# Mandatory. Name of the enrichment type.
'name' => 'ApolloRPA_CompanyDomainToLeads',
# Description of what does this enrichment type do.
'description' => 'Using Apollo RPA for Getting the Email, Phone, Job Postion, Facebook and Company of al managers, directors, owners, founders, presidents and C-level people of a company.',
# Optional. Thunbnail of the RPA in action.
'picture_url' => 'file://home/leandro/code/mass/extensions/mass.subaccount/public/mass.subaccount/images/enrichment-type/Apollo_LinkedInUrlToEmail.png',
# Mandatory. What type of profile is required to run this enrichment.
# Such a value must exists in the array of profiles hash descriptors.
'profile_type' => :'Apollo_RPA',
# Optional. If true, this scraping role is available for end-users to setup in the UI.
# Default: true.
'available' => true,
# Allow user to setup one or more parameters (aka: on-the-fly filters).
# Reference: https://github.com/MassProspecting/docs/issues/82
parameters => "keyword;",
# Example: this is an example of all supported parameters
#parameters => "email_verification_result;email;phone;linkedin;facebook;english_names_only;keyword;industry;headcount;revenue;country;sic;naics;location;",
})
Apply filters in the moment of sending an outreach or performing and enrichment.
outreach_type
orenrichment_type
.Mass::Parameters
.update
to_h
outreach_type.parameters
.enrichment_type.parameters
.action.id_filter
.parameters
to classesaction
.rule
does.update
Filter.update
properly.rules/new
screen.rules/:id
screen.outreach
andenrichment
.to_h
should return the parameters configured in the action that generated such an outreach or enrichment.Filter.upsert
method to delete existing filters that are not in the new hash descriptor.