A

Adobe Commerce

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

Other
1
Actions
0
Triggers

Example

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

type == "lead"key →TriggerNew LeadWebhookAssignmulti_objective_scoreStrategysales-teamassignedadobe_commerceActionDelivered
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("adobe_commerce", "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

API keyNo auth

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

Actions

No actions on this connector.