Sending Automatic Emails with Conga

When describing the automatic sending of emails using Conga products, we're referring to any method that delivers the email over the API rather than via the user interface. These API delivery methods are:

  • Composer in background mode (DS7=12 parameter value)
  • Conga Batch
  • Conga Trigger

Required Email Parameters

  • &EmailToId=[Contact ID]
  • &EmailTemplateId=[Salesforce Email Template ID] or &CongaEmailTemplateId=[Conga Email Template ID] (the &CETID)
    • If you're using a Salesforce email template, you must also use the &TemplateId parameter to specify a document template.
    • If you're using a Conga Email Template, a document template is optional.

Optional Email Parameter

  • &EmailRelatedToId=[Object ID]
    • If using a Salesforce Email Template, the merge fields that are available for use on that template are fields from the Object referenced in the &EmailRelatedToId parameter. Contact fields also merge if you've included the &EmailToId=[Contact Id].
    • Specifies which record to relate the Salesforce email task, not the task that Conga may create as part of activity logging. The Salesforce email task always starts with "Email:" and can be related to two records: 1) the Contact to which the email was sent, and 2) the record to which the &EmailRelatedToId parameter is set.
    • This parameter defaults to the Master record if not specified otherwise in the URL button/formula.
    • Can't Specify a Contact as the Email Recipient? Use this workaround for not using &EmailToId:
      • If you are unable to specify a Contact ID as the primary recipient of the email using &EmailToId, the work-around solution is to omit the email template and send the recipient an email with a Subject, Attachment, and no Body (in other words, the body of the email is blank but has a subject line and a document attachment, created by Conga Composer). The recipient is specified using an email address rather than a Contact ID.
  • You can omit &EmailToId if these parameter instructions are followed:
    • EXCLUDE:

      &EmailRelatedToId=[Object ID]
      &EmailTemplateId=[Salesforce Email Template ID] or &CongaEmailTemplateId=[Conga Email Template ID] (a.k.a. &CETID)

    • INCLUDE:

      &EmailSubject=[Text]
      &EmailAdditionalTo=[Email Address(es)]

  • Composer can customize the From: address of an email with two different parameters:
    • &EmailFromId=[Org-wide email address]
      • Set to the Salesforce ID of an active Org-wide email address, that's it!
      • Set to the Salesforce ID of an active User (not a Contact!)
      • Alters two properties of the email message: 1) the DisplayName (the name that is associated to the "from" address), and 2) the Reply To (the email address to which replies are sent)
      • Your email appears to come from the User specified (because we change the Display Name)
      • If the recipient clicks Reply in their inbox, they reply to the User specified (because we changed the ReplyTo)
      • The DisplayName property is not editable when using SendGrid.
      • This parameter does not affect the From attribute of the message, which is the actual email address from which the email is sent.
      • The actual From property of the message contains the email address of the person who: clicked the Composer button, scheduled Conga Batch, or is the User to Send As of the workflow outbound message specified in Conga Trigger.&EmailReplyToId=[User ID]

Salesforce API Email Limitations

  • 24-hour email limit: Salesforce limits you to a certain number of emails which can be sent through the API per day. ***Contact Salesforce Support for details on the limitation of your instance***

  • Once the daily API email limit is exceeded, the Composer/Conga Batch/Conga Trigger process will return an error, "Problem: ERROR: Email delivery failed: SINGLE_EMAIL_LIMIT_EXCEEDED.Failed to send email."
  • In order to work around these Salesforce limits, a customer should integrate SendGrid email delivery service in their Conga Composer solution(s).