Running Activepieces Locally with Docker for Drupal Workflow Testing

Staff Reporter

Tutorial written on a piece of paper lodged in a typewriter — Markus Winkler / Unsplash

Dries Buytaert has published a guide explaining how to run Activepieces locally using Docker, enabling developers to build and test workflows connected to their local Drupal environments without requiring internet exposure.

The guide outlines how Activepieces can be used as an open source alternative to services like Zapier or n8n, facilitating workflows between Drupal and external platforms such as Slack, Google Sheets, or Salesforce. Developers working locally with tools like DDEV can use Docker to run Activepieces on http://localhost:8080, allowing direct integration with their Drupal sites without tunneling tools like ngrok.

The setup uses a single Docker command to run Activepieces with in-memory queue processing and a SQLite database, mapping local data to the ~/.activepieces directory. Buytaert notes that while this configuration supports workflow testing, it does not permit modifications to Activepieces or the bundled Drupal Piece. Contributors intending to work on the Drupal integration itself must use the full development setup instead. The article also provides steps for upgrading the Docker container as new versions of Activepieces are released.

Reference: Running Activepieces locally with Docker by Dries Buytaert

Docker

Guide

Testing

Drupal Integration

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.