Skip to content
Drupal logoNuelink logo

Connect Drupal to Nuelink

Move data between Drupal and Nuelink the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Drupal triggers
3
Drupal actions
6
Nuelink triggers
1
Nuelink actions
7

Automation ideas

What you can build with Drupal and Nuelink

A few flows teams run between Drupal and Nuelink. Use one as a starting point, or build your own from scratch.

  • Polling by ID in Drupal creates Create Post in Collection in Nuelink

    A trigger that polls the Drupal site by ID.

  • New Published Post in Nuelink creates Call Service in Drupal

    Fires when Nuelink publishes a post to a channel (or fails to, if you choose Failed). Runs once per channel.

  • Polling by ID in Drupal creates Update Post in Nuelink

    A trigger that polls the Drupal site by ID.

  • New Published Post in Nuelink creates Create Entity in Drupal

    Fires when Nuelink publishes a post to a channel (or fails to, if you choose Failed). Runs once per channel.

  • Polling by ID in Drupal creates Delete Post in Nuelink

    A trigger that polls the Drupal site by ID.

  • New Published Post in Nuelink creates List Entities in Drupal

    Fires when Nuelink publishes a post to a channel (or fails to, if you choose Failed). Runs once per channel.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Drupal and acts in Nuelink, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.