C

Checkr Partner

Checkr Partner connector for Ductor — available as both a trigger and a destination.

Legal
1
Actions
1
Triggers

Example

A complete route that uses Checkr Partner — an input is matched, scored by a strategy, assigned, and dispatched to Checkr Partner.

type == "lead"key →TriggerNew LeadWebhookAssignmulti_objective_scoreStrategysales-teamassignedcheckr_partnerActionDelivered
Show the code
// Route a new lead to the right owner and open the record.
engine.Route(ductor.Route{
Match: `routable.type == "lead"`,
Strategy: "multi_objective_score",
Pool: "sales-team",
Then: ductor.Workflow{
Mode: ductor.Async,
Steps: ductor.Steps{
ductor.Connector("checkr_partner", "run"),
},
},
})
 
// Durable, observable, exactly-once.
decision, err := engine.Dispatch(ctx, routable)

What you can build

Route by rule

Match any input with CEL and send it to the right pool.

Fan out to many

Scatter to several connectors and gather the results.

Trigger a workflow

Kick off a sync or async workflow on every routed item.

Authentication

OAuth 2.0No auth

Credentials are stored AEAD-encrypted at rest — usable by the engine, never readable back.

Actions

No actions on this connector.

Triggers

No triggers on this connector.