Skip to main content
Conga Support

Anatomy of a Conga Composer Button

There are two types of Composer buttons: non-OAuth and OAuth (Open Authorization).

Non-OAuth Buttons

All non-OAuth Conga Composer® URLs start the same way. The first three lines are identical in every Composer URL, and the fourth line is customized to identify the Master Object from which you’ll be gathering data and running the solution. These first lines are referred to as the Base URL, which look like this:


OAuth Buttons

OAuth (Open Authorization) is a different security protocol that is required for all Conga Composer buttons created in the Salesforce Lightning user interface.  The Base URL of an OAuth button looks like this:


In both button types, the &Id= parameter (or &id= in the OAuth button) defines your master object – the Salesforce® object from which you will launch your Composer solution. The value of this parameter will always be the ID of your master object. For example:

To launch the solution from this type of object: The fourth line would contain:
Account &id={!Account.Id}
Opportunity &id={!Opportunity.Id}
Case &id={!Case.Id}
A custom object &id={!CustomObjectName_c.Id}

Conga Composer includes sample buttons on all standard objects.

Composer Parameters

After the Base URL, you will see the Composer parameters that have been added to the Composer solution (assuming they have been added by the Conga Admin).  Parameters are settings that control the behavior of your solution.  They always use the following convention: &ParameterName=Value.

In the example below, you can see seven parameters have been added to this Composer button URL:




The parameters in this example control template selection, output file type, output file name, and where to save a copy of the output document.  For more information about parameters, see Customizing Composer with Parameters and the Parameter Guide.

How to Populate Parameter Values

There are three ways to populate parameter values:

  1. Type the value into the parameter (using Solution Manager or manually).
  2. Using a Salesforce merge field (such as {!Opportunity.Id}, which will dynamically update with a value when the solution is run.
  3. Using a Qvar, which allows you to retrieve data with a Conga Query and then pass that data to another parameter to use as the value.

See Composer button URL examples for more examples.

  • Was this article helpful?