Get Company Factors

securityscorecard.get_company_factors
ActionBusiness appsconnection required

Calls the SecurityScorecard API with the connection's credentials.

Read a company's per-factor scores and the issue counts behind them.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
SecurityScorecard
Secret shape
the API token, or {"api_token": "…"}
Config it needs
base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
scorecard_identifier
The company's primary domain, which is how SecurityScorecard identifies a scorecard.
stringYes——example.com
severity
Return only issues of this severity in each factor's issue summary.
stringNo—one of "high", "medium", "low", "info", "positive"—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "scorecard_identifier": "example.com"
}

Output

One shape.

result

FieldTypeExample
factors
One entry per scoring factor.
array—
factors[].name
The factor's id, such as network_security.
string—
factors[].score
The factor's score from 0 to 100.
number—
factors[].grade
The factor's letter grade.
string—
factors[].grade_url
A URL to an image of the factor's grade.
string—
factors[].issue_summary
The issue types found for the factor, with counts.
array—
count
How many factors the response carried.
number—
scorecard_identifier
The company the factors were read for.
string—
{
  "count": 0,
  "factors": [
    {
      "grade": "",
      "grade_url": "",
      "issue_summary": [],
      "name": "",
      "score": 0
    }
  ],
  "scorecard_identifier": ""
}

See Get Company Factors run in a workflow.

In a technical demo we add the SecurityScorecard connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.