API: next field in automations, new NOW() function, EMA credit transfer and fixes

The GET /pipelines/{id}/actions and GET /pipelines/{id}/actions/{actionId} endpoints now return a next field for each step containing the IDs of the following steps, so the full automation graph can be reconstructed from the response. For most step types, next is an array of IDs (usually one, or empty/null at the end of a branch). For branching steps, next is an object with one array of IDs per output ‑ yes / no for the Condition step, the variant keys for the Split test step, and default / quarantine_skip for the Send email step.

A new GET /feeds endpoint returns the list of all product feeds in the account, including the feed type, URL, number of loaded products, and any error from the last processing run. The id field from the response can be used as feed_id for the feed refresh endpoint.

The POST /templates endpoint now accepts an mjml field in addition to html, using the same JSON format as the Ecomail template editor. A template created from an MJML definition is fully editable in the drag‑and-drop editor ‑ Ecomail compiles the definition to HTML automatically. A template created from raw HTML remains editable only in the code editor. The html and mjml fields cannot be combined ‑ exactly one must be sent.

Alongside the existing CURDATE() function, NOW() is now available, returning the current date and time in the format YYYY‑MM-DD HH:MM:SS. The Date field type now accepts this extended format with time in addition to the plain date ‑ useful for more precise logging, for example the exact time of a registration or purchase.

Agency admins can now transfer EMA credits between the agency account and sub‑accounts the same way it already works for email and SMS credits ‑ in both directions, in the Manage sub‑account section. A transfer cannot be made if the agency or the affected sub‑account currently has an unsettled EMA session in progress (chat or a scheduled checkup) ‑ in that case you need to wait for it to finish.

When a segment with an Exclude from segment condition was used as a parent segment, the resulting segment ignored that exclusion and returned contacts that should have been excluded. Exclusion from a parent segment is now respected.

The time of the last sent campaign in the Overview section was displayed in UTC, while the Campaigns section showed the same moment in local time (CET/CEST). Time display in the Overview is now unified with the rest of the app.

For some orders from the Eshop‑rychle integration, the product code stored with the order differed from the code in the product catalogue, so the product could not be matched in the data feed. Codes are now stored consistently and matching against the catalogue works reliably.

Exporting an automation with a large number of steps and contacts could fail or take an unreasonably long time. Export processing is now optimised and handles large automations reliably.