Automation Module

Das Automation-Modul ist die Zapier-Schicht von aYOUne. Du definierst Triggers (was passiert), Pipelines (was passiert dann), und Webhooks (wo wird's hingeschickt). Routing: automation-api.ayoune.app.

Hauptentitäten

Webhooks

Outbound-Hooks für Plattform-Events. Vollständig dokumentiert unter Developer Portal → Webhooks.

ay create webhooks "ERP-Sync" \
  --set events='["consumers.created","consumers.updated"]' \
  --set url=https://hooks.example.com/incoming \
  --set secret=<32+chars>

Pipelines

Multi-Step-Workflows. Eine Pipeline besteht aus einer Reihe von Steps, jeder mit Input/Output und Bedingungen.

Step-Typ	Zweck
`trigger`	Startpunkt: Event-Match
`condition`	If/Else basierend auf Event-Daten
`transform`	JSONata oder JS-Expression
`http`	Externer HTTP-Call
`db`	CRUD auf eigene Collections
`notification`	Mail/SMS/Push absetzen
`wait`	Delay (für Drip-Campaigns)
`subPipeline`	Andere Pipeline aufrufen

Beispiel: "Wenn neuer Consumer mit Premium-Tag → Welcome-Mail + Slack-Notification + Task an Account-Manager":

name: premium-onboarding
trigger:
  event: consumers.created
  filter: { tags: { $in: ["premium"] } }
steps:
  - id: send-welcome
    type: notification
    channel: mail
    template: premium-welcome
    to: ""

  - id: notify-slack
    type: http
    method: POST
    url: ""
    body: { text: "Neuer Premium-Consumer: " }

  - id: create-task
    type: db
    collection: tasks
    op: create
    data:
      title: "Premium-Onboarding für "
      assignedTo: ""
      priority: high

Triggers

Ein Trigger ist ein wiederverwendbarer Event-Filter, der mehrere Pipelines starten kann.

Trigger-Typ	Beispiel
`event`	`consumers.created`, `tasks.assigned`
`cron`	`0 9 * * MON` (Montags 9:00)
`webhook`	Eingehender HTTP-Call (Public-URL pro Trigger)
`manual`	Per UI/CLI gestartet

Custom-Functions

Für komplexe Transformationen reicht JSONata nicht. Custom Functions sind sandboxed JavaScript-Snippets, die im custom-functions-worker ausgeführt werden:

// fn:dedupe-tags.js
module.exports = (input) => {
  const tags = input.tags || [];
  return { ...input, tags: [...new Set(tags)] };
};

Deploy via:

ay functions create "dedupe-tags" --file ./dedupe-tags.js
ay functions deploy dedupe-tags
ay functions invoke dedupe-tags --input '{"tags":["a","b","a"]}'

In einer Pipeline aufrufen via Step-Typ function.

Pipeline-Run-History

Jeder Pipeline-Lauf wird in pipelinetuns festgehalten:

Feld	Hinweis
`pipeline`	Ref
`triggeredBy`	event/cron/manual/webhook
`status`	`running` / `success` / `failed`
`steps[]`	Pro Step: input, output, duration, error
`totalDuration`	ms

Best Practices

Idempotenz: Steps so designen, dass sie ohne Schaden 2x laufen können (Webhook-Retries!).
Timeouts: Jeder HTTP-Step hat einen Default-Timeout von 30s — bewusst hochsetzen, wenn nötig.
Testen: ay exec automation:dry-run --pipeline <id> --input '{...}' simuliert ohne Side-Effects.

Verbindungen

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Help me set this up Step by step, asking me as you go.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Help me with a problem Narrow down the cause instead of guessing.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Explain it in plain words No jargon, from the ground up.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

A checklist to tick off To follow along while you do it.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Build it into my project Concrete code for my use case.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/api-reference/automation-module.md
The complete collection: https://ayoune.com/en/docs/api-reference.md

Help me build this into my project.

- First ask me about language, environment and what I am trying to achieve.
- Then give a minimal, runnable example — no ellipses standing in for code.
- Name the error cases I must handle and how they surface.
- State the limits: timeouts, quotas, permissions.

Use only what the source actually describes. Do not invent fields, parameters
or endpoints — an invented call costs me more time than it saves.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)