# nCino Webhooks

## Webhooks for Auto Triggering nCino CI Jobs <a href="#title-text" id="title-text"></a>

Refer to [Webhooks](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks) for configuration details. Currently, nCino supports the following webhooks:

1. Webhook for GitHub
2. Webhook for GitHub Enterprise
3. Webhook for Microsoft Azure
4. Webhook for GitLab
5. Webhook for Bitbucket
6. Webhook for Bitbucket Enterprise
7. Webhook for Visual Studio GIT
8. Webhook for Visual Studio GIT Enterprise

For the above-mentioned repositories, if you select **“Trigger Build on Auto-Commit,”** the job will be triggered automatically for every new commit to the branch.

{% hint style="warning" %}
**Important Note**: If you’re committing both *nCino Record-Based Config* files and *Salesforce Metadata* files to the same branch—even though they’re in separate folders—AutoRABIT may encounter an issue with certain Git-based version control systems. Specifically, AutoRABIT is unable to determine which folder's contents have changed, leading to unnecessary build triggers that won't pick up any changes if they are in an irrelevant folder when the 'Build on commit' option is enabled.
{% endhint %}

### Configuring the CI Job for Trigger Build on Commit <a href="#manually-creating-records" id="manually-creating-records"></a>

1. Toggle the slider in the highlighted selection to enable 'Trigger Build on Commit' for the respective job.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FGuUNWpjqLCuAQGBCwcm8%2Fimage.png?alt=media&#x26;token=02bf8715-097d-4001-8e61-d0b13f145656" alt=""><figcaption></figcaption></figure>

2. Observe the copy symbol beside the URL. Use the highlighted URL as 'payload URL' in the configuration settings of the webhook. Refer to the following page for help configuring the [webhook](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/webhooks).
3. Once a job is created with the 'Trigger Build on Commit' setting enabled, then every commit into the respective repository and branch will auto-trigger a run in the application.

### Using Supported Deployment Types

For the *Revision Range* deployment type, the `TriggerBuildOnCommit` option is **not supported**, which is expected behavior. When using a defined "From" and "To" revision, the system has no new revisions to detect or upon which to trigger builds. As a result, `TriggerBuildOnCommit` functionality does not apply to Revision Range deployments.

**Supported Deployment Types for** `TriggerBuildOnCommit`

The `TriggerBuildOnCommit` option is available for the following deployment types only:

1. **Version Control with Baseline Revision**: Suitable for deployments requiring specific baseline comparison.
2. **Entire Branch**: Triggers on new commits to the entire branch, allowing continuous integration.
3. **Version Control using Salesforce**: Integrates directly with version control but uses Salesforce to detect and trigger builds on commits.

If your deployment uses *Revision Range*, `TriggerBuildOnCommit` will not apply. If triggering builds on commits is required for your workflow, consider using one of the supported deployment types listed above.

### Manually Committing Templates <a href="#manually-creating-records" id="manually-creating-records"></a>

To manually commit the template data into your version control system (outside of AutoRABIT), follow the steps below:

#### **Information to collect before committing:** <a href="#information-to-collect-before-committing" id="information-to-collect-before-committing"></a>

* **HEXID**: A random 8-character alphanumeric string, for example: 10cPkE0E
* **Feature-Org-Id**: Provided by AutoRABIT upon request, for example: rJA5XMqsT71C6AwhaA7jyHznMxXvpRSM

#### Steps to Commit New Templates: <a href="#steps-to-commit-new-templates" id="steps-to-commit-new-templates"></a>

1. Add the HEXID and Feature-Org-Id details in the following files (refer to the attached sample file for guidance):
   * `feature-templates/nCino/config/manifest.yaml`
   * `feature-templates/nCino/config/project-def.json`
2. Create a feature folder named using the format `hexId-featureName` and include all relevant details such as filters, data, object sets, buckets, object relationships, and user IDs.
3. Ensure all information follows the folder structure of the reference folder.
4. Add `ar-config/project-def.json` file at root folder as in the attached reference.

#### Steps to Modify Existing Templates: <a href="#steps-to-modify-existing-templates" id="steps-to-modify-existing-templates"></a>

1. For any record additions, deletions, or updates, make the necessary changes under:
   * `feature-templates/nCino/dataset/hexId-FeatureName/data`
2. To modify object filters, make adjustments under:
   * `feature-templates/nCino/dataset/hexId-FeatureName/filters`

{% hint style="info" %}
Note:

* In the case of GitHub and GitLab, the jobs will only trigger if the commit has any changes related to “feature-templates.”
* For any version control types other than GitHub and GitLab, the CI Jobs will trigger for every commit regardless of data changes.
  {% endhint %}

## Understand the Folder Structure:

Follow the defined folder structure when creating new branches in Git to maintain consistency and standardization across repositories. The following is the standard folder structure.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FF3CJa9lfv5cf9ep0dsWb%2FScreenshot%202025-08-18%20at%205.36.26%E2%80%AFPM.png?alt=media&#x26;token=edbf892b-7acb-45d1-985e-53d0861d1143" alt=""><figcaption></figcaption></figure>

Refer to the attached ZIP file for the above recommended folder structure.

{% file src="<https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F4rzu7gR9NALLnZvMhevX%2FCommitStructure.zip?alt=media&token=1f4cad3e-0256-469a-bc06-fe6f4bffe87d>" %}

### Individual File Structures

The configuration files—`manifest.yaml`, `project-def`, the corresponding data file `1_nFORCE__Brand__c`, and the filter file `nFORCE__Brand__c`—must adhere to the following folder structure.

1. manifest,yaml

   ```yaml
   !!com.rabit.featuremigration.beans.vcstructure.ConfigManifest
   packageDirectories:
     packagePaths:
       dataset:
         features:
           <HEXID>-<Template Name>:
             path: dataset/<HEXIA>-<Template Name>
             prefix: <UserPrefix>
             standardFeature: True/False
             versions:
               '4.0':
                 modifiedDate: '2025-08-18 09:06:55'
   ```
2. project-def

   ```json
   {
     "name": "<REPO NAME>",
     "defaultPath": "dataset",
     "featurePrefixes": {
       "<HEXID>": "<FEATUREORGID>"
     }
   }
   ```
3. 1\_nFORCE\_\_Brand\_\_c.json

   ```json
   {
     "name": "1_nFORCE__Brand__c",
     "attributes": [
       "Id",
       "OwnerId",
       "IsDeleted",
       "Name",
       "CreatedDate",
       "CreatedById",
       "LastModifiedDate",
       "LastModifiedById",
       "SystemModstamp",
       "LastViewedDate",
       "LastReferencedDate",
       "nFORCE__Brand_Custom_CSS__c",
       "nFORCE__Brand_JSON__c",
       "nFORCE__Description__c",
       "nFORCE__Is_Applied__c",
       "nFORCE__Look_Up_Key__c",
       "nFORCE__LookupKey__c",
       "AutorabitExtId__c",
       "Description__c"
     ],
     "records": {
       "1": {
         "AutorabitExtId__c": "",
         "CreatedById": "0058c00000BxeO9AAJ",
         "CreatedDate": "2025-08-18T09:04:38.000Z",
         "Description__c": "",
         "Id": "a1uKa000000NwxxIAC",
         "IsDeleted": "false",
         "LastModifiedById": "0058c00000BxeO9AAJ",
         "LastModifiedDate": "2025-08-18T09:04:38.000Z",
         "LastReferencedDate": "2025-08-18T09:04:41.000Z",
         "LastViewedDate": "2025-08-18T09:04:41.000Z",
         "Name": "Record-01",
         "OwnerId": "0058c00000BxeO9AAJ",
         "SystemModstamp": "2025-08-18T09:04:38.000Z",
         "nFORCE__Brand_Custom_CSS__c": "",
         "nFORCE__Brand_JSON__c": "",
         "nFORCE__Description__c": "",
         "nFORCE__Is_Applied__c": "false",
         "nFORCE__Look_Up_Key__c": "42406995856406363",
         "nFORCE__LookupKey__c": ""
       },
       "2": {
         
       }
     }
   }
   ```
4. nFORCE\_\_Brand\_\_c.json

   ```json
   {
     "name": "nFORCE__Brand__c",
     "query": "Select Id From nFORCE__Brand__c Where Id \u003d \u0027a1uKa000000NwxxIAC\u0027"
   }
   ```