Agentic workflows

Follow up on what changed.

Build journeys that check current data, choose a relevant action and send a personal email. Let maxinja build the steps.

Example · Morrow Running

Delivered orderRidge trail shoes

Running preferenceTrail running

Complete the running kit

Workflow

Select a step to inspect its instruction.

What Nadia receivesPersonal paragraph

Morrow Running

A runner following a rocky coastal trail in a red jacket

A match for your running kit.

Hi Nadia,

For your Ridge trail shoes and rocky coastal trails, consider the Ridge-compatible gaiter. It fits the Ridge shoe attachment points and helps keep loose grit out.

Explore your matching gear

See current sizes, availability and product details in the store.

Follow the decision

Your strategy, carried through every step.

Read the context. Choose the next move. Keep it personal.

QueryRead the context.

Query customers, orders and activity together.

AIMake a considered choice.

Give AI a question and a defined answer.

LogicTake the right path.

Branch on the facts and the AI result.

AdaptyleMake the email personal.

Adaptyle writes from the context you supply.

ActionsKeep your tools in sync.

Update records, fire events or call an API.

From your brief to a published journey.

Example workflowMorrow Running

Your brief

After a shoe delivery, wait fourteen days. Check what they kept and skip anyone who bought another accessory. Choose a relevant product they don’t own and explain why it fits.

maxinja

A post-purchase journey, ready for your review.

Delivery event Wait 14 days Query + AI Personal email

Draft

The whole customer, at every decision.

Bring people, orders and evaluated attributes into the same journey. A Query step reads your current workspace data; an AI step works with the context you give it.

Customer context

NadiaTrail running

Delivered order: Ridge trail shoes
Accessory history: Trail socks

Built for how customers actually behave.

Start from a real signal. Choose the timing, the conditions and what happens next.

Start when something matters.

A purchase, a changed record, a date or a webhook can bring a customer into the journey.

TriggerOrder delivered

orderId: order_1042

Post-purchase follow-up

Wait for the right moment.

Set a delay or calculate a date from customer data. The next step resumes when that wait ends.

Order delivered

DelayWait 14 days

Give customers time to use what they bought.

Check for a later purchase

Different customers. Different paths.

Use If/Else for a decision or Switch for several routes. Your conditions decide who continues.

Switchcustomer.plan

Go beyond the email.

Save the decision to a record, fire a business event or pass context to another system.

Update Record

Save the recommendation.

recommendedProduct: Ridge gaiter

Customer record updated

One follow-up for every item in a list.

For Each starts a separate run for each item. Follow up on related accounts, bookings or records with their own context.

Three recordsFor Each

Run for record ARun for record BRun for record C

Explore the workflow blocks.

Triggers7

Scheduled Timestamp: Start once at a chosen date, or on publication when no date is set.
Record Created or Updated: Start when a contact or object record enters your chosen criteria.
Record Deleted: Respond when a matching contact or object record is removed.
Event Fired: Start from a purchase, signup or another event your application records.
Email Event: Respond to an open, click, delivery or other selected email activity.
Evaluated Attribute Threshold: Start when an evaluated attribute’s value crosses a configured threshold.
Incoming Webhook: Receive a JSON payload from another system to start the journey.

Context and AI5

Find Records: Find matching contacts or objects, together or in a separate run for each record.
Set Value: Calculate a value from data already in the journey, such as a date or total.
Query: Look up workspace records, counts or aggregates and pass the answer to later steps.
AI: Generate a structured answer, with optional web search, read-only workspace queries and selected MCP tools.
For Each: Process a collection by starting an independent run for each item.

Conditions and timing3

If/Else: Choose between two paths using a condition on the customer context.
Switch: Choose a named path, including weighted random choices for A/B/n tests.
Delay: Wait for a duration or a date calculated from the customer’s data.

Actions5

Create or Update Records: Save customer or object data using the information gathered by the journey.
Delete Records: Remove matching records and continue once their deletion has finished.
Fire Event: Record a business event that another configured workflow can respond to.
HTTP Request: Call another system and use its JSON response in later steps.
Send Email: Send the step’s email template, with Adaptyle personalization and optional engagement follow-ups.

Know what happened. Right down to the step.

Open a run to see where it went, what each step received and what it returned. Find waits and failures without guessing.

Run historyExample runs

Event FiredDelayQueryAISend Email

Send Email

The recommendation became an email.

Input: Product: Ridge gaiter
Output: Template: Complete the kit

Edit a draft. Keep the live version.

Publish a new version when it is ready. Runs already in progress stay on the version they started with.

Pause when you need to.

Pause a workflow from its controls. Review the journey and its run history before you continue.

Keep the handoff visible.

Inspect each step’s inputs, outputs, timing and errors in run history.

Workflow guide

Build the follow-up you have in mind.

Book a demo Meet maxinja Workflow guide