The Targeting Local CRM integration with SendGrid allows you to send emails from your SendGrid account based on triggers that you configure in Targeting Local CRM. Get your SendGrid API Key here. You can also use tokens to include activity data from Targeting Local CRM in emails that you send from SendGrid. Create HTML emails in SendGrid here. Here are six HTML SendGrid templates.
Connecting Targeting Local CRM to SendGrid: 20:00 – 40:00 Min
Connecting Targeting Local CRM to SendGrid
- Navigate to Settings → Integrations → SendGrid.
- Enter the API key for your SendGrid account.
- Click Save API Key.
Sending Emails with Triggers
- Click Manage Triggers (or navigate to Calls → Triggers). If you do not already have a trigger in your account, you will be directed to a new settings page. Otherwise, click New Trigger in the upper right.
- Enter a name and optional description for your trigger.
- Use the drop-down menu to select when you would like this trigger to run.
- Select to have the trigger run for all activities or assign specific traffic numbers to this trigger.
- Click +Add Workflow.
- Select the rules that should apply to this trigger. You may wish to set rules for calls over a certain duration, or to only have a trigger run for first-time contacts.
- Click Add Action and select Send Email via SendGrid.
- Enter the email address to send to in the “To:” field.
- To use the email address already associated with the contact record in Targeting Local CRM, leave this field blank. If you choose this option and the contact record does not have an email address, no message will be sent.
- You can enter multiple email addresses here (up to 255 characters).
- Enter the address the email should be sent from in the “From:” field. This can be any email address you choose.
- Enter the name the email should be sent from in the “From Name:” field. This can be any name you choose.
- Use the “SendGrid Email Template” drop-down to select which of your SendGrid templates you would like to use for this email.
- Click Save Changes.
Including Targeting Local CRM Data in SendGrid Templates
When creating templates in SendGrid, you can use {{tokens}} to insert activity data from Targeting Local CRM into the email message. The following is a complete list of tokens that can be used:
- id
- sid
- account_id
- name
- cnam
- search
- referrer
- location
- source
- source_id
- source_sid
- tgid
- likelihood
- duration
- direction
- talk_time
- ring_time
- hold_time
- parent_id
- street
- city
- state
- country
- postal_code
- called_at
- unix_time
- tracking_number_id
- tracking_number_sid
- tracking_number
- tracking_label
- dial_status
- is_new_caller
- indexed_at
- last_location
- inbound_rate_center.country
- inbound_rate_centerprefix
- inbound_rate_center.tollfree
- billed_amount
- billed_at
- caller_number_split
- contact_number
- excluded
- redacted
- tracking_number_format
- caller_number_format
- alternative_number
- caller_number_complete
- caller_number_bare
- tracking_number_bare
- caller_number
- visitor
- call_path.route_name
- call_path.route_id
- call_path.route_type
- call_path.started_at
- call_path.started_at
- left_talk_time
- right_talk_time
- transfers
- call_status
- status
- spotted.spot_id
- spotted.keyword
- spotted.start
- spotted.user
- spotted.marked
- spotted.marked_at
- salesforce
- audio
- transcription
- transcription_text
- custom_fields.numbers
- custom_fields.floats
- custom_fields.strings
- custom_fields.dates
- custom_fields.pickers
- custom_fields.bools
- callbacks
- emails
- webvisit.score
- webvisit.keywords
- webvisit.referrer_host
- webvisit.referrer_path
- webvisit.location_host
- webvisit.location_path
- webvisit.browser
- webvisit.device
- webvisit.mobile
- day
- month
- hour
- ga.utmz
- ga.utma
- ga.utmb
- ga.utmc
- ga.medium
- ga.campaign
- ga.cid
- ga.events
- visitor_ip
- tag_list
- notes
- latitude
- longitude
- extended_lookup_on
- inputs.menu_inputs
- inputs.geo_inputs
- carrier
- spam.risk
- spam.score
- sale.name
- sale.score
- sale.conversion
- sale.value
- sale.date
- agent_id
- agent.name
- agent.email
- agent.id
- agent.pic_url
- legs.started_at
- legs.to
- legs.from
- legs.status
