Skip to main content
Conga Support

Schedule Conga Conductor to Run Automatically

The final touch in your Conga Conductor solution may be to schedule the Conductor events to execute automatically, on a schedule. Scheduling Conga Conductor means that a user does not have to manually launch the batch but rather Conductor looks for batches that are queued to run on a scheduled basis and runs them for you.

The ability to run a batch of records on a scheduled basis without user oversight or intervention potentially poses a great risk. For example, once scheduled, you could inadvertently send hundreds of documents, communications, and/or eSignature requests to external recipients. Please thoroughly test your solution and confirm it’s working correctly before scheduling it to run automatically.

You must utilize the Conga Conductor record (not a List View button) in order to run the Conductor solution on a scheduled basis.

As a best practice, you should schedule your Conductor solution to run at least 15 minutes apart. Scheduling multiple Conductor solutions at the same time can have unexpected results.

To schedule Conga Conductor to run automatically:

  1. Click the Conductor Setup tab.

  2. Enable the Scheduled Conductor Master Switch and click Save Changes.

  3. Click Create Salesforce Token.

    The user who clicks the Create Salesforce Token button is under whose authority Scheduled Conductor will operate.

    The Salesforce Token for Conga Conductor will be listed in Salesforce under that user’s My Settings > Personal > Advanced User Details > OAuth Connected Apps.

    If the user revokes the Salesforce Refresh Token (in Salesforce Setup, under OAuth Connected Apps), all scheduled Conga Conductor records will cease to operate on a scheduled basis.

  4. Open the Conductor record that you wish to schedule and click Schedule.

  5. Select a Frequency of Daily, Weekly, or Monthly.

    The Repeat section changes depending on the Frequency you choose.

    The Status message at the bottom of the screen provides helpful hints and updates as you navigate through the steps of the Scheduler.

  6. Choose the Start Date, End Date and time of day (Preferred Start Time) to run the scheduled batch merge.

    The date displays in U.S. formatting (month/day/year). Note that the time zone displayed is based on the running user’s time zone.

  7. Click Save Changes.

  8. Click the Enable button.

    The Disable button will deactivate the schedule while the Unschedule button will delete the schedule information.

    The Schedule section on the Conductor record displays the details of the schedule and provides a visual reminder to users that this Conductor record runs on a schedule. Your Conductor record will now run on an automatic, scheduled basis.

The Content Workspace ID field is only used when a Scheduled Conductor operation is set to deliver the output files by download (&QMode=Download). In this case, you must populate the ID of a Salesforce Content Library (formerly called Content Workspace) so that the files have somewhere to be stored since the merge operation runs in the background.

Errors that occur during a scheduled event are logged as child records to the Conductor Record in the Scheduled Conductor History related list; the errors also appear on the Conductor Dashboard.

  • Was this article helpful?