B

Bliro

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

Communication
1
Actions
0
Triggers

Example

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

type == "lead" && value > 5000key →TriggerNew LeadWebhookAssignyield_optimizedStrategyae-westassignedbliroActionApprovaldeal-deskApprovalDelivered
Show the code
// When a high-value lead lands, pick the best rep and ping them.
engine.Route(ductor.Route{
Match: `routable.type == "lead" && attrs.value > 5000`,
Strategy: "yield_optimized",
Pool: "ae-west",
Then: ductor.Workflow{
Mode: ductor.Async,
Steps: ductor.Steps{
ductor.Connector("bliro", "run"),
ductor.Approval("deal-desk"),
},
},
})
 
// Durable, observable, exactly-once.
decision, err := engine.Dispatch(ctx, routable)

What you can build

Speed-to-lead alerts

Score an inbound lead and ping the assigned rep within seconds.

On-call escalation

Route a P1 to the right engineer and notify their channel.

Deal-won broadcast

Celebrate closed-won deals to the whole team automatically.

Authentication

OAuth2 client credentialsNo auth

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

Actions

No actions on this connector.