Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Drupal

Drupal integration for Flows360 workflows.

CategoryBusiness Intelligence
Authenticationcustom
Version1.1.10
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Drupal with Flows360

Drupal integration for Flows360 workflows.

Use the Drupal connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 3 triggers.

Available actions

  • Call Service
  • Create Entity
  • List Entities
  • Get Entity
  • Update Entity
  • Delete Entity

Available triggers

  • Polling by ID
  • Polling by timestamp
  • Webhook

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Drupal
  • Package: @activepieces/piece-drupal@1.1.10
  • Exact artifact digest: sha256:cdabd26b7109445ec9d8bda43c787a75556ed06927cd28b7b15cc7a5c2aa227c
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Call Service (drupal-call-service), Call a service on the Drupal site Classification: read.
  • Create Entity (drupal-create-entity), Create a new entity in Drupal with smart field discovery and validation Classification: read.
  • List Entities (drupal-list-entities), List entities from Drupal using JSON:API Classification: read.
  • Get Entity (drupal-get-entity), Retrieve a single entity by UUID Classification: read.
  • Update Entity (drupal-update-entity), Update an existing entity in Drupal with smart field discovery and validation Classification: read.
  • Delete Entity (drupal-delete-entity), Delete an entity from Drupal Classification: read.

Trigger contracts

  • Polling by ID, polling.
  • Polling by timestamp, polling.
  • Webhook, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions6
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Website URL Required
  • Username Required
  • Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Call Service Yes No Call a service on the Drupal site
Create Entity Yes No Create a new entity in Drupal with smart field discovery and validation
List Entities Yes No List entities from Drupal using JSON:API
Get Entity Yes No Retrieve a single entity by UUID
Update Entity Yes No Update an existing entity in Drupal with smart field discovery and validation
Delete Entity Yes No Delete an entity from Drupal
Polling by ID Yes No polling trigger declared by the pinned package.
Polling by timestamp Yes No polling trigger declared by the pinned package.
Webhook Yes No webhook trigger declared by the pinned package.

Supported actions

Call Service · Read

Call a service on the Drupal site

drupal_call_service · Risk: low · Retry: safe

Inputs

  • service · string · Required, The service to call.
  • config · object · Required
Create Entity · Read

Create a new entity in Drupal with smart field discovery and validation

drupal_create_entity · Risk: low · Retry: safe

Inputs

  • entity_type · string · Required, Choose the type of content to create.
  • entity_fields · object · Optional, Fill in the content fields. Available fields depend on the entity type selected above.
List Entities · Read

List entities from Drupal using JSON:API

drupal_list_entities · Risk: low · Retry: safe

Inputs

  • entity_type · string · Required, Choose what type of content to list.
  • published_status · string · Optional, Filter by publication status
  • sort_by · object · Optional, Choose how to sort the entities
  • sort_direction · string · Optional
  • limit · number · Required, Maximum number of entities to retrieve (0 = all entities)
  • output_options · object · Optional
Get Entity · Read

Retrieve a single entity by UUID

drupal_get_entity · Risk: low · Retry: safe

Inputs

  • entity_type · string · Required, Choose the type of content to retrieve.
  • entity_uuid · string · Required, The unique identifier (UUID) of the specific content item to retrieve.
Update Entity · Read

Update an existing entity in Drupal with smart field discovery and validation

drupal_update_entity · Risk: low · Retry: safe

Inputs

  • entity_type · string · Required, Select the entity type and bundle
  • entity_uuid · string · Required, The UUID of the entity to update
  • entity_fields · object · Optional, Update the values for the entity fields (only provide values for fields you want to change)
Delete Entity · Read

Delete an entity from Drupal

drupal_delete_entity · Risk: low · Retry: safe

Inputs

  • entity_type · string · Required, Choose the type of content to delete.
  • entity_uuid · string · Required, The unique identifier (UUID) of the specific content item to delete.

Triggers

Polling by ID · Poll

A trigger that polls the Drupal site by ID.

Inputs

  • name · string
Polling by timestamp · Poll

A trigger that polls the Drupal site by timestamp.

Inputs

  • name · string
Webhook · Webhook

A webhook that the Drupal site can call to trigger a flow.

Inputs

  • id · string

Setup

Setup

  1. Add the Drupal connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Website URL (website_url), required.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-drupal@1.1.10; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Drupal connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-drupal@1.1.10 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com