Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

MongoDB

MongoDB integration for Flows360 workflows.

CategoryDeveloper Tools
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect MongoDB with Flows360

MongoDB integration for Flows360 workflows.

Use the MongoDB 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 7 actions and no declared triggers.

Available actions

  • Find Documents
  • Insert Documents
  • Update Documents
  • Delete Documents
  • Find and Update Documents
  • Find and Replace Documents
  • Aggregate Documents

Available triggers

  • No triggers are declared in this pinned package.

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: MongoDB
  • Package: @activepieces/piece-mongodb@0.1.6
  • Exact artifact digest: sha256:a8b216709546e9fc70f6b6ff107e70272ff65fbfb300b66af56cbb0687653a8e
  • 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

  • Find Documents (find_documents), Find documents in a collection Classification: read.
  • Insert Documents (insert_documents), Insert one or more documents into a collection Classification: read.
  • Update Documents (update_documents), Update multiple documents in a collection Classification: read.
  • Delete Documents (delete_documents), Delete documents from a collection Classification: read.
  • Find and Update Documents (find_and_update_documents), Find documents and update them, returning the updated documents Classification: read.
  • Find and Replace Documents (find_and_replace_documents), Replace documents that match a filter with a new document Classification: read.
  • Aggregate Documents (aggregate_documents), Perform aggregation operations on documents in a collection Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects7
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Host Required
  • Use MongoDB Atlas URL Format Required
  • Database Optional
  • Username Required
  • Password Required · protected credential
  • Auth Source Optional

Supported objects

ObjectReadWriteNotes
Find Documents Yes No Find documents in a collection
Insert Documents Yes No Insert one or more documents into a collection
Update Documents Yes No Update multiple documents in a collection
Delete Documents Yes No Delete documents from a collection
Find and Update Documents Yes No Find documents and update them, returning the updated documents
Find and Replace Documents Yes No Replace documents that match a filter with a new document
Aggregate Documents Yes No Perform aggregation operations on documents in a collection

Setup

Setup

  1. Add the MongoDB 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:
  • Host (host), required.
  • Use MongoDB Atlas URL Format (useAtlasUrl), required.
  • Database (database), optional.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  • Auth Source (authSource), optional.
  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-mongodb@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 0 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required MongoDB 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-mongodb@0.1.6 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