Automate AI work from one JSON definition of a trigger, its conditions, and its steps. When Messaging receives an email, for example, Conjoin can classify it, look up the customer's order, and draft a reply within one workflow.
In one workflow, you can chain Inference calls, Context queries, and calls to other Conjoin services such as Messaging. Conjoin executes those steps in order and passes each step's output to the steps that follow it.
Conjoin starts a workflow as soon as its trigger event occurs, whether that event is an email in Messaging, an upload to Storage, or a webhook call from your own system.
Conjoin evaluates each condition against an AI classification or a value in the event data and continues on the branch that matches.
A step can call Inference, query Context, or classify text. Its input can come from the trigger event or from any earlier step.
Call Messaging, Storage, Billing, and other Conjoin services from a workflow step. For example, one step can send a customer the reply that an earlier AI step drafts, as an email through Messaging.
Set how many times Conjoin retries a failed step. When a step still fails after its last retry, Conjoin can move the workflow to a fallback path or notify you.
Conjoin pauses the workflow at an approval step, such as one that you place before a payout, until a person reviews the action. Your code then resumes the workflow through the API.
Conjoin pauses the workflow at an approval step, such as one that you place before a payout, until a person reviews the action. Your code then resumes the workflow through the API.
Steps that you define in JSON
Set how many times Conjoin retries each step
Inputs, outputs, and timing per step
Trigger a workflow on every email that Messaging receives. In that workflow, an AI step classifies the intent of each email. Conjoin then takes the branch for that category, where a step can forward the email to the team that owns it or answer it with a generated reply.
One workflow definition contains the classification, the routing, and the replies.
When someone uploads an invoice to Storage, an AI step extracts the supplier, the amount, and the due date. A validation step checks those fields against your rules before the final step writes a record to Database.
Conjoin passes the invoice fields from the extraction step through validation to the database write, so the only call that your application makes is the upload.
Place an approval step before an action such as issuing a refund or emailing a whole customer list. Conjoin notifies the approvers, then holds the workflow until one of them approves or until the timeout that you configure expires.
A person can review the action that an AI step proposes before Conjoin performs it.
Conjoin records the input, the output, and the timing of every step in each execution. To test a fix, replay a failed execution from any step with changed inputs before the trigger event occurs again.
When a step fails, you can compare its recorded input and output to find the cause.
Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.