n8n

I’d treat the binary volume as a first-class backup target alongside the database dump, not as an afterthought. A restore test should bring up both the database and that volume together; otherwise the workflows may load while their file payloads are missing.

Very cool to have this natively in n8n

the async polling thing is the real pain in n8n . you end up with a wait node loop that looks ugly and breaks if the timeout is off by even a little.

make sure your error branch actually parses the status code separately from the body, most 500s from image hosts have useful info in the response body that n8n just doesnt surface by default

I still keep n8n around for dumb glue though - cron scrapes, slack alerts, that kind of thing. Building THOSE with an agent is more effort than it's worth. Visual for the boring stuff, code for anything with state.

You can close the parent-to-child gap without a timestamp search: have each sub-workflow return its own execution id from its last node. Execute Sub-workflow hands that back to the caller, so the parent can write its execution id and the child's into the same log row and the chain becomes a direct join instead of a time window.

The built-in parent/child view is fine for one hop. It stops being useful the moment several runs overlap, which sounds like where you are.

n8n encrypts credentials at rest, but it doesn't care whose API keys are inside them — if the Stripe/database/API credentials in the workflows belong to your personal accounts instead of the client's, the handover is a lie and everything breaks the day you revoke them. Provisioning every credential from the client's accounts before go-live, and documenting which service each credential belongs to, has saved me more than one "why did payments stop working" call six months later.

So we’d still need the explicit logs for both success and cases where the decision looks off, but the Error Trigger approach is still useful if there’s an actual workflow failure.

In our case, the workflow itself won’t necessarily throw an error since a wrong decision can still be a successful execution. So we’d still need the explicit logs for both success and cases where the decision looks off, but the Error Trigger approach is still useful if there’s an actual workflow failure.

I’d add the external monitor to the handover. If it stays in your account, alerts go to you after the contract ends. In didit.run you can hand the workspace to the client and the ping urls stay the same.

I was checking how others handle this in the n8n community, and maintaining a separate log seems like the better approach. I was initially thinking more about being able to navigate from the main workflow execution directly to the corresponding sub-workflow execution trace, similar to how the editor tab lets you navigate to the sub-workflow itself. Having the parent execution ID/correlation metadata exposed on the sub-workflow execution would make this much easier, especially for evaluation runs.

The built in parent/child stuff in n8n is kinda spotty once you get past one level deep. Half the time the execution list just shows them as separate unrelated runs so good luck piecing it together after the fact

n8n's parent/child link works until you're looking at 200 executions in a five-minute window.

By default n8n holds file payloads in memory and writes them to PostgreSQL as base64, which quickly triggers container OOM crashes and balloons database backup sizes as soon as workflows handle PDFs or images.

Offloading binaries to the filesystem keeps memory usage predictable and makes database dumps much faster.

This is a solid workflow, especially the structured output part.

Ask Fetchsandbox for the twin's signing secret and store it as a separate n8n credential/variable alongside the base URL, so sandbox vs live is one toggle, not two.

If you verify incoming webhooks against the wrong secret, everything fails closed and it looks like n8n just silently dropped the events.

n8n is just one of many automation methods.. and been replaced altogether in my shop.

idempotency key built from the chat message id fixed it, not the gate

mine double fired because the classifier call on synexa stalled and n8n retried the whole branch

pour whatsapp, devis et publication, commence par n8n en self-host plutôt qu'un agent orchestrateur, ce sont surtout des workflows fixes avec une étape LLM au milieu.

In n8n's WhatsApp Trigger node, I don't see any place to manually enter/match that same verify token — the node just has OAuth credentials (Client ID/Secret) and a Trigger On (Messages) dropdown. So I'm not sure how n8n is supposed to validate the token Meta sends during the handshake.

The message buffering part is probably the most useful piece here. WhatsApp users almost never send a complete request, in one message so waiting briefly before triggering the agents make the interaction feel much more natural.

if you're doing this in n8n specifically, its built-in Credentials store already handles the agent-never-sees-the-raw-key part (credentials are referenced by ID, not injected into the workflow JSON), but it doesn't do rotation or per-agent scoping on its own

The message-buffering part is especially useful since real WhatsApp conversations rarely happen in a single message.