Skip to main content
Conga Support

SendGrid Integration Parameters

This page contains links to the parameters belonging to this category. If you need more information about parameters in general and how to use them, visit the following links:

Before You Start: A Few Rules About Parameters  |  Adding Parameters to a Solution  |  How Parameters are Formatted

Background

SendGrid is an email delivery service with features that assure customers an extremely high deliverability rate at a low cost.  Delivering emails via SendGrid means customers can circumvent Salesforce email limits.

SendGrid is available separately from their website. You must subscribe to that service to use this integration.

Setup the SendGrid Integration.

  1. Subscribe to a plan on the SendGrid website.
  2. Configure your SendGrid account according to their instructions.
  3. Open the Conga Setup page (located on the lower-right corner of the Conga Composer dialog box).
  4. On the Integration Partners tab, paste your SendGrid username and password.  The credentials are encrypted and stored securely.
  5. Save your changes.

Once Conga is configured with your SendGrid credentials, all email generated through Conga will be delivered via SendGrid. Conga Composer will also automatically create a completed Task record for each email sent through SendGrid.

From the Conga Composer dialog box, when the Email button is clicked, Conga Composer generates the output document (as usual) and then presents an editable email, pre-addressed to the email address configured in the Conga Composer button.


To enable the use of merge fields in your email templates use a Conga Email Template OR configure a SendGrid Template (from their website). Do not use Salesforce email templates, merge fields are not compatible with Salesforce email templates and SendGrid.

Parameters

Conga Composer's Email Parameters and Conga Email Templates work with SendGrid.

DS7 enables merge operations to occur in the background.

LGAttachOption sets the Salesforce object to which attachments generated during Activity Logging are stored.

SC1 defines where a copy of the merged output file will be stored.

SCMEndpoint configures the Conga Composer button to connect to a specific SpringCM endpoint.

SCMPreview displays the SpringCM document preview window after the merge process completes.

SCMVisible makes the SpringCM button visible on the Conga Composer dialog box.

  • Was this article helpful?