Capability

Workflows

Connect Caymland to all your systems: fetch, check, reshape and pass on data, triggered by events, webhooks or schedules. Built visually, with the real data visible at every step.

See all features
Workflows

Campaigns guide people. Workflows move data.

Starts when it should.

Manually, on a schedule, through a webhook, on an event in Caymland or from inside another workflow.

Sees the real data.

Every step shows what went in and what came out, as a table, JSON or schema. Drag fields straight into the next step.

Records what ran.

Every run with status, duration and the data of each step. A failed run can be repeated with the same data.

Watch

Workflows in 2 minutes

There is a gap between your systems

Your campaigns guide contacts through your communication. That covers a large part of daily work, but not all of it.

Next to it sit the tasks that happen between systems: an order from the shop needs processing. A form submission should land in the sales channel, sorted into business customer or private person. Every night, data should be fetched from a business system, checked and passed on. And a request should be classified by AI before a person reads it.

Until now there were two ways to do this: a developer, or a second automation tool your data then also has to pass through.

Workflows are the third way. They are part of Caymland M4, built in the same system with the same permissions, and your data stays there.

Campaigns guide people, workflows move data

The two are deliberately separate:

  • A campaign accompanies a contact over days and months: who gets which message when, who moves to which stage, who collects points.
  • A workflow carries data through a chain of steps in seconds: fetch, check, reshape, pass on. Every step sees what the previous one delivered.

That a background automation cannot accidentally interfere with your customer communication is no coincidence. It is built that way.

What starts a workflow

  • Manually, with your own test data, whenever you run it.
  • On a schedule, every minute, every night or every Monday at seven, in your time zone.
  • Through a webhook, when another system calls in. The workflow accepts the call immediately or answers straight away with the result.
  • On an event in Caymland M4: a contact is saved or deleted, their points change, a form is submitted, an email opened, a page visited.
  • From inside another workflow, as a sub-workflow that returns its result.

The event slows nothing down: Caymland queues the run and carries on without delay.

What happens in between

You assemble the flow in the builder. The building blocks cover everything a data flow needs:

  • Control the flow. Conditions with sixteen comparisons, routing to up to eight paths, merging by position or key, loops over records, waiting from seconds to days, and sub-workflows for anything you need more than once.
  • Reshape data. Set and rename fields, filter, sort, limit, split, aggregate and remove duplicates until the data has the shape the next system expects.
  • Calculate and decide. Expressions in every field work with text, numbers, lists and dates. Where that is not enough, your own code step takes over.
  • Talk to systems. HTTP requests to any API, authenticated by user and password, token, header, API key or OAuth2. Ready-made connectors for services such as Slack, Stripe and OpenAI, and the selection keeps growing.
  • Use AI. Summarise texts, classify requests, extract details and translate, as a step in the middle of the data flow.

Build without guessing

  • Every step shows the real data, as a table, JSON or schema: what went in and what came out.
  • Drag fields from the previous step's data straight into the next one.
  • Test individual steps right in the builder; a test run shows status, number of records and duration on every node.
  • Notes on the canvas explain what a section does, so the workflow still makes sense a year from now.
  • Switch steps off temporarily, undo, copy and paste, including between workflows.
  • Templates for typical processes to start from, and existing workflows can be brought in as JSON.

When something goes wrong

An automation that fails silently is worse than none. So:

  • For each step you decide whether it retries or continues despite the error.
  • An error workflow receives the details of every failed run and notifies whoever you choose.
  • Every run is saved after each step. If something fails, it resumes where it was.
  • Every run is recorded: when it started, what triggered it, how long it took and what went in and out of every step, with the real data. Repeat a run with one click instead of recreating the error.

Built to be secure and to scale

  • Credentials are stored encrypted and separate from the workflows, with their own permission. They cannot be read out through the API.
  • Outgoing calls only go to public addresses. Internal networks and system addresses are blocked.
  • Permissions control who sees, builds and runs workflows and who may manage credentials.
  • Concurrent runs can be limited per workflow, waiting runs use no computing time, and the run log cleans itself up according to your retention periods.
  • Your data stays in Caymland, hosted in Switzerland or Germany, instead of passing through yet another service.

What this looks like day to day

The new lead. A form is submitted. The workflow checks whether the address belongs to a company or a free email service and posts business customers straight to the sales team's Slack channel.

The incoming order. The shop reports an order by webhook. The workflow splits it into line items, removes duplicate articles, calculates the totals and returns the summary straight away.

The weekly report. Every Monday at seven a workflow fetches the week's figures, calculates open and click rates, sorts them and posts the top three to the team's channel.

AI in the data flow. A request arrives by webhook. AI summarises and classifies it, and the workflow passes it on to the right system.

Questions & answers

Frequently asked questions

01

How is this different from campaigns?

A campaign accompanies a contact through your communication over days and months. A workflow carries data through a chain of steps in seconds and connects systems. Rule of thumb: if it is about a contact's lifecycle, use a campaign. For everything else, use a workflow.

02

Do we need an additional automation tool?

No. Workflows are part of Caymland M4, with their own builder, run log and permissions. Your data does not pass through another service.

03

Which systems can we connect?

Any system with an API, through HTTP requests with all common authentication methods up to OAuth2. Ready-made connectors exist for services such as Slack, Stripe and OpenAI, and the selection keeps growing.

04

Can we add our own logic?

Yes. Expressions work with text, numbers, lists and dates right inside every field, and where that is not enough you write your own code step.

05

What happens if a step fails?

For each step you decide whether it retries or continues despite the error. Every run is saved after each step and resumes where it was after an interruption. You repeat failed runs with one click, and a dedicated error workflow can notify you straight away.

06

Where are the credentials for external systems kept?

Encrypted in Caymland, separate from the workflows and with their own permission. They cannot be read out through the API, and editing a credential only replaces the stored secret if you explicitly do so.

07

Can a workflow wait?

Yes, for seconds, hours or days, or until a specific time. A waiting run uses no computing time while it waits.

08

Can we bring existing workflows along?

Yes. Workflows can be pasted and copied as JSON, including between workflows, and templates for typical processes are ready to use.

The difference in one sentence

Other systems need a second tool for this.Caymland M4 has it built in.

See all features