Buildkite and SecurityScorecard Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Buildkite and SecurityScorecard matched by integrating their events and actions. When developer tools events happen in Buildkite, update the SecurityScorecard automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Buildkite and SecurityScorecard

Detailed info you need to know about Buildkite and SecurityScorecard integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Buildkite

    • Developer Tools
    • 2 triggers
    • 70 searches
    • 78 actions

    Continuous integration and delivery platform for running fast, secure pipelines.[5]

  • SecurityScorecard

    • Developer Tools
    • 1 trigger
    • 72 searches
    • 63 actions

    Monitor company security scores, portfolios, issues, and vendor risk.[6]

How to connect Buildkite to SecurityScorecard

Set up your Buildkite and SecurityScorecard integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Buildkite and SecurityScorecard work in WEXTL?

WEXTL exposes actions and triggers for Buildkite and SecurityScorecard that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Buildkite triggersSecurityScorecard actions

Buildkite modules

  • Add a Cluster Maintainer Makes a user or a team a maintainer of a cluster. Use User or Team ID with the UUID of the user from List Members or of the team from List Teams.
  • Add a Pipeline Webhook Registers a Buildkite webhook on the repository of a pipeline and reports Success with the Pipeline.
  • Add a Team Member Puts a member of the organization into a team under a given Role. Returns the team membership with its Created at time and User.
  • Add a Team Pipeline Links a pipeline to a team at a chosen Access Level. Returns the link with its Created at time.
  • Add a Team Suite Gives a team access to a test suite at a chosen Access Level and returns the link with its Created at time.
  • Archive a Pipeline Archives a pipeline. Unarchive a Pipeline reverses it.
  • Cancel a Build Cancels a build of a pipeline and returns the canceled build with its State and Number.
  • Cancel a Job Cancels one job of a build and returns it with its Type, Name and Step key.
  • Create a Build Triggers a build for a Pipeline at a Commit on a Branch. Add Environment Variables and Meta Data, or Pull Request fields, to shape the run.
  • Create a Build Annotation Writes an annotation with a Body on the page of a build, with a Style and a Context. Turn on Append to extend an existing one.
  • Create a Cluster Creates a cluster with a Name to group agents and queues. Use Emoji and Color to style it, and Maintainers (JSON) to set who maintains it.
  • Create a Cluster Secret Stores a secret Value in a Cluster under a Key that builds use to read it. Add a Policy to attach an access policy.
  • Create a Hosted Queue Sets up a queue on Buildkite hosted agents of the chosen Instance Shape, under a Key, inside a Cluster.
  • Create a Job Annotation Writes an annotation with a Body on one job, with a Style and Priority. Turn on Append to extend an annotation that has the same Context.
  • Create a Pipeline Sets up a pipeline from a Name, a Repository and a Configuration (YAML). Use Default Branch to name the main branch, Tags to label it and Skip Queued Branch Builds to drop queued builds of a branch when a newer build starts.
  • Create a Pipeline Schedule Schedules recurring builds of a pipeline on a Cron Line, labeled with Label. Set Branch and Commit to choose what each scheduled build runs.
  • Create a Pipeline Template Saves a Name and Configuration (YAML) as a template. Turn on Available to offer it when people create pipelines.
  • Create a Pipeline Trigger Gives a pipeline an incoming trigger under a Label. Use Build (JSON) for the build settings, Verification (JSON) for a verification secret, and choose the Type carefully because it cannot be changed after creation.
  • Create a Rule Adds an organization rule of one Type with the Value (JSON) that defines it.
  • Create a Self-Hosted Queue Sets up a queue under a Key for agents you run yourself, inside a Cluster. Turn on Use GitHub App Token to use that token for checkouts.
  • Create a Team Starts a team in the organization under a Name. Turn on Members Can Create Test Suites to let its members create suites.
  • Create a Test Suite Creates a test suite in Test Engine with a Name. Use Team IDs to give teams access to it and Show API Token to get the suite API token back once.
  • Create an Agent Token Issues a token that lets agents register in a Cluster. Use Allowed IP Addresses to limit where it works from, Expires At to set an end date, and Allowed Queue IDs or Allow All Queues for queue access. The token value is shown only once.
  • Create Invitations Invites people by their Emails to join the organization, with a Role and optional Teams.
  • Delete a Build Annotation Removes an annotation from the page of a build in Buildkite.
  • Delete a Cluster Deletes the cluster that groups agents and queues in your organization.
  • Delete a Cluster Secret Removes a secret that was stored for the agents of a cluster.
  • Delete a Job Annotation Deletes an annotation that appears on the page of one job.
  • Delete a Job Log Removes the log output that a job produced.
  • Delete a Pipeline Deletes a pipeline that builds a repository in your Buildkite organization.
  • Delete a Pipeline Schedule Removes a recurring schedule from a pipeline.
  • Delete a Pipeline Template Removes a pipeline template from the templates of your Buildkite organization.
  • Delete a Pipeline Trigger Removes an incoming trigger from a pipeline.
  • Delete a Queue Removes an agent queue, hosted or self-hosted, from its cluster.
  • Delete a Rule Deletes one rule that is set on the organization.
  • Delete a Team Disbands a team defined in your organization.
  • Delete a Test Suite Deletes a test suite recorded in Test Engine for your organization.
  • Delete an Artifact Deletes an artifact that a job uploaded.
  • Disable the GitHub Webhook Processing Stops Buildkite from acting on GitHub webhooks for a pipeline.
  • Enable a Test Turns a test back on after it was muted or skipped. The returned test has its Scope and Name.
  • Enable the GitHub Webhook Processing Lets Buildkite act on GitHub webhooks for a pipeline again.
  • Find a Test Looks up a test in a Test Suite through its Scope and Name, returning matching tests with their ID and Web url.
  • Get a Build Fetches a single build. Turn on Include Jobs to add its jobs, or Include Test Engine Data to add Test Engine data to the output.
  • Get a Cluster Opens a cluster and reports its Default queue id, Name and Description.
  • Get a Cluster Maintainer Pulls one maintainer entry of a cluster, showing whether the Actor type is a user or a team and its Actor id.
  • Get a Cluster Secret Returns the settings of a cluster secret, such as its Key, Description and Policy.
  • Get a Job Loads one job and returns its Type, Name and Step key.
  • Get a Job Log Downloads the output a job logged, with its Content, Size and Header times.
  • Get a Member Opens an organization member and shows their Role and Sso mode.
  • Get a Pipeline Retrieves a pipeline and shows its Name together with its URL and Web url.

SecurityScorecard modules

  • Add a Company to a Portfolio Registers one company in a portfolio. Add Companies by Domain reaches the same endpoint. Use Additional Fields to attach extra JSON.
  • Add a Tag to a Company Applies a scorecard tag to a company, using the company Domain and the tag Id.
  • Add a Tag to a Group Places a scorecard tag inside a tag group, through the tag groups part of the API.
  • Add Companies Bulk Uploads companies to portfolios in one bulk-upload request. Use Additional Fields to send the company list as JSON.
  • Add Companies by Domain Puts a company into a portfolio, using the company Domain. Add a Company to a Portfolio calls this same endpoint.
  • Add Tags Bulk Creates tags for all companies in one bulk-create request. Use Additional Fields to list the tags as JSON.
  • Create a Bulk Search Job Starts a bulk search job over companies, running on the bulk-searches resource with the Search text.
  • Create a Custom Scorecard Builds a new custom scorecard. Use Additional Fields to pass its settings as JSON.
  • Create a Custom Scorecard Filter Set Defines filters for a custom scorecard. Use Additional Fields to hand over the filter JSON.
  • Create a Custom Scorecard Source Set Sets up sources for a custom scorecard. Use Additional Fields to include the source JSON.
  • Create a Feedback Validation Adds a validation to feedback, served by feedback/validations. Use Additional Fields to give its details as JSON.
  • Create a Portfolio Creates a portfolio in SecurityScorecard, which can then receive companies through the portfolio companies endpoint.
  • Create a Scorecard Invitation Link Creates a scorecard invitation by posting to the invitations endpoint, the one Create an Invitation also uses. Use Additional Fields to attach the JSON body.
  • Create a Scorecard Tag Adds a new scorecard tag to the scorecard-tags collection. Use Additional Fields to pass the tag settings as JSON.
  • Create a Tag Group Makes a group for scorecard tags through the tag groups resource. Use Additional Fields to supply group settings as JSON.
  • Create an Invitation Sends an invitation, served by the invitations resource. Use Additional Fields to give the invitee details as JSON.
  • Delete a Custom Scorecard Deletes a custom scorecard from SecurityScorecard by its Id.
  • Delete a Feedback Validation Removes the feedback validation with the matching Id from feedback/validations.
  • Delete a Followed Company Removes a company from the all-companies list by its Domain.
  • Delete a Portfolio Deletes a portfolio, addressing the portfolios route with a Portfolio Id.
  • Delete a Scorecard Tag Removes a scorecard tag through the scorecard-tags route.
  • Delete a Tag Group Deletes a tag group, addressing the scorecard-tags groups collection.
  • Delete an Invitation Deletes an invitation that SecurityScorecard stores in its invitations list.
  • Delete Filters Clears every filter set up on a custom scorecard.
  • Delete Followed Companies in Bulk Deletes several followed companies in one request on the bulk-delete route. Use Additional Fields to list them as JSON.
  • Delete Sources Empties the source list of a custom scorecard.
  • Delete Tags Bulk Removes tags in a single request on the bulk-delete route. Use Additional Fields to list the tag details as JSON.
  • Download a Report Retrieves a generated report with its Report Id. Get a Report Status reads the same endpoint.
  • Edit a Portfolio Changes a portfolio. Use Additional Fields to send settings as JSON.
  • Edit a Tag Group Edits a tag group. Use Additional Fields to send group settings as JSON.
  • Find Followed Companies Finds the companies in the all-companies list. Use Maximum Number of Results to cap the count.
  • Generate a Company Events Report Starts a company events report, served by the reports resource. Use Additional Fields to pass the report options as JSON.
  • Generate a Compliance CSV Exports compliance data as a CSV via reports/compliance/csv/export. Use Additional Fields to pass options as JSON.
  • Generate a Detailed Report Builds a detailed report through reports/detailed. Use Additional Fields to set the report options.
  • Generate a Footprint Domains CSV Requests a CSV of footprint domains from reports/footprint-domains. Use Additional Fields for the report options.
  • Generate a Footprint IPs CSV Produces a CSV of footprint IP addresses from the reports/footprint-ips endpoint.
  • Generate a Full Scorecard Report Requests the full scorecard report as JSON from the reports/full-scorecard-json endpoint.
  • Generate a Partnership Report Creates a partnership report on reports/partnership. Pass options as JSON with Additional Fields.
  • Generate a Portfolio Report Asks SecurityScorecard to build a portfolio report. Use Additional Fields to send report options.
  • Generate a Summary Report Requests a summary report from reports/summary, with options as JSON via Additional Fields.
  • Generate an Issues Report Starts an issues report on reports/issues. Use Additional Fields to tune it.
  • Get a Bulk Search Job Reads one bulk company search job that was started earlier.
  • Get a Company Grade Reads a company from the main companies endpoint, using its Scorecard Identifier. Get a Company Score and Get a Company Summary read the same endpoint.
  • Get a Company History Score Loads the score history of a company from history/score, which Get Company History Scores Series reads as well.
  • Get a Company Score Returns a company from the main companies collection, matching its Scorecard Identifier. Get a Company Grade reads this too.
  • Get a Company Summary Looks up a company in the main companies collection for its Scorecard Identifier. Get a Company Score reads this too.
  • Get a Custom Scorecard Loads one custom scorecard by Id through custom-scorecards of SecurityScorecard.
  • Get a Domain Footprint Reads footprint data for one Domain in the footprint area of SecurityScorecard.
  • Get a Factor Score Loads the score of one Factor for a company, using a Scorecard Identifier.
  • Get a Followed Company Looks up a followed company in the all-companies list by Domain and returns its list entry.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Buildkite and SecurityScorecard integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Buildkite and SecurityScorecard on WEXTL®

Claim your 3-day trial to build Buildkite with SecurityScorecard integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Buildkite and SecurityScorecard.

How do I connect Buildkite and SecurityScorecard?

Connect your Buildkite and SecurityScorecard accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Buildkite and SecurityScorecard?

Example: when the "Watch Builds" trigger in Buildkite fires, WEXTL can "Add a Company to a Portfolio" in SecurityScorecard. Buildkite has 2 triggers (including Watch Builds and Watch Events). SecurityScorecard has 135 actions (including Add a Company to a Portfolio, Add a Tag to a Company, and Add a Tag to a Group). Add filters and transforms between steps when you need them.[1]

Can Buildkite trigger actions in SecurityScorecard, and SecurityScorecard in Buildkite?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Buildkite and SecurityScorecard?

No. Buildkite-to-SecurityScorecard automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Buildkite integrate with SecurityScorecard in real time?

Yes. Trigger-based automations start the moment Buildkite (or SecurityScorecard) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Buildkite + SecurityScorecard integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Buildkite with SecurityScorecard?

You can build your Buildkite + SecurityScorecard automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Buildkite and SecurityScorecard integration.

  1. Buildkite and SecurityScorecard integration source code, module specs and credentials implementation.
  2. Our Buildkite and SecurityScorecard integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Buildkite and SecurityScorecard, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Buildkite integration information
  6. SecurityScorecard integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Buildkite and SecurityScorecard integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Buildkite and SecurityScorecard, or get started