On GitHub, you can take a look at the source code, or read through the existing issues to see if somebody else had a similar problem. If you're still stuck, feel free to create a pull request or open an issue yourself!
The Sync Contacts with SendGrid Firebase extension will automatically sync contact data to your SendGrid marketing campaigns contact list based on information from documents added to a specified Cloud Firestore collection.
Adding a document triggers this extension to add a contact to the Marketing Campaigns contact list. Updating a document will update the contact's data and deleting the document will trigger its removal from the contact list in SendGrid.
Here's an example document that would trigger this extension:
_10admin.firestore().collection('contacts').add({_10 email: 'someone@example.com',_10 first_name: 'Bob',_10 last_name: 'Bobson'_10});
You can install the extension using either the Firebase console or the Firebase CLI. To install or manage extensions, you must be assigned either the Owner, Editor or Firebase Admin role. Your Firebase project must also be on the Blaze (pay as you go plan).
Before you install the extension you will need to do the following:
Create a collection in Firestore for your contacts
This extension listens for changes to documents in a Cloud Firestore collection that you specify. When it finds a new document, it creates a new contact in SendGrid, when a document is edited the contact is updated and when the document is deleted the contact is removed. You can use any Cloud Firestore collection for this purpose.
Set up security rules for your contacts document collection.
This extension can be used to create, update and delete contacts directly from client applications. However, you should carefully control client access to the collection to avoid potential abuse. Adding a contact to your list will trigger any automations you have set up for the list and you don't want users able to add new contacts to your without their permission.
Security rules will vary from application to application, but you should always make sure that only contacts that have signed up to join your list are added to the collection.
Make sure you have the latest version of the Firebase CLI and you have your Firebase project ID or alias to hand.
Run this command to install the extension:
_10firebase ext:install twilio/sendgrid-sync-contacts --project=projectId-or-alias
The command will prompt you for details like your SendGrid API Key and the name of a the Cloud Firestore collection you want to use.
Once installation is complete, check out the instructions below for how to use the extension.
Visit the Firebase Extensions directory to find the Sync Contacts with SendGrid extension, or install the extension directly here. Click Install and follow the on-screen instructions to install the extension. The installation process will prompt you for the details you collected earlier, including your SendGrid API key and the name of your Cloud Firestore collection.
After installation, this extension monitors all document writes to the collection you configured. Contacts are added, updated, or deleted based on the contents of the document's fields.
To create a new contact with the minimal data, add a document to your messages collection with an email field.
_10{_10 email: "test@example.com"_10}
You can add any of the following fields to your document and they will be applied to your contact:
| Field | Type | |
|---|---|---|
| string | required | |
| alternate_emails | Array<string> | |
| first_name | string | |
| last_name | string | |
| address_line_1 | string | |
| address_line_2 | string | |
| city | string | |
| postal_code | string | |
| state_province_region | string | |
| country | string | |
| phone_number | string | |
| string | ||
| line | string | |
| string | ||
| unique_name | string | |
| custom_fields | Map<string, string> |
custom_fields must be defined within your SendGrid account and are a map of the custom field's ID to the content.
On GitHub, you can take a look at the source code, or read through the existing issues to see if somebody else had a similar problem. If you're still stuck, feel free to create a pull request or open an issue yourself!