All Collections
Using Clayton with Copado
Using Clayton with Copado

Use Clayton in conjunction with Copado to add Clayton's powerful scanning to your Copado pipelines

Gabriele Gallo Stampino avatar
Written by Gabriele Gallo Stampino
Updated over a week ago

The Copado integration allows users to scan user stories with Clayton and automate repetitive code review tasks on Salesforce developments.

Before we start

If you don't have a Clayton account, please sign up here.

Clayton scanning capabilities

When working with user stories, it's key to make sure new developments and configuration changes are not going to introduce security flaws or code quality problems.

Our Copado integration supports both the validation of the proposed changes for each user story (via pull request) and a full scan of the specific user story branch.

Pull request validation

Each user story can be validated using pull requests, and for every new PR created, Clayton launches a scan of the proposed changes.

Clayton's feedback is published in the User Story at the end of the validation phase.


For every scan triggered, a Result object is created in the User Story, including the outcome:

  • PASSED: if no issues have been detected

  • PASSED_WITH_WARNINGS: only issues with WARNING severity detected

  • NOT_PASSED: blocker issues detected (ERROR, CRITICAL)

Pull Request Reviews

Reviews are published inside a related object called Pull Request.

2) Full-feature scan

It is also possible to validate the entire feature branch and scan

3) Diff Scan for User story validation

The Diff Scan option is available to validate only the changes committed in the User Story.

Scans can be triggered manually, or automatically via webhook.



Did this answer your question?