Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Discourse

Modern open source forum software

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Discourse with Flows360

Modern open source forum software

Use the Discourse 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 no declared triggers.

Available actions

  • Create Post
  • Create Topic
  • Change User Trust Level
  • Add Users to Group
  • Send Private Message
  • Custom API Call

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: Discourse
  • Package: @activepieces/piece-discourse@0.2.0
  • Exact artifact digest: sha256:3519d8caddde62eea94c8035ae5db0751eeb6830a63dac3a6cca646450f3da4c
  • 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

  • Create Post (create_post), Create a new post in discourse Classification: read.
  • Create Topic (create_topic), Create a new topic in Discourse Classification: read.
  • Change User Trust Level (change_user_trust_level), Change the trust level of a user Classification: read.
  • Add Users to Group (add_users_to_group), Add users to a group Classification: read.
  • Send Private Message (send_private_message), Send a private message in Discourse Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

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

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • API Username Required
  • Website URL Required

Supported objects

ObjectReadWriteNotes
Create Post Yes No Create a new post in discourse
Create Topic Yes No Create a new topic in Discourse
Change User Trust Level Yes No Change the trust level of a user
Add Users to Group Yes No Add users to a group
Send Private Message Yes No Send a private message in Discourse
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Post · Read

Create a new post in discourse

create_post · Risk: low · Retry: safe

Inputs

  • raw · string · Required, Content of the post
  • topic_id · string · Required, ID of the topic to post in
Create Topic · Read

Create a new topic in Discourse

create_topic · Risk: low · Retry: safe

Inputs

  • title · string · Required, Title of the Topic
  • raw · string · Required, Content of the topic
  • category · string · Optional, ID of the category to post in
Change User Trust Level · Read

Change the trust level of a user

change_user_trust_level · Risk: low · Retry: safe

Inputs

  • user_id · string · Required, ID of the user
  • new_trust_level · string · Required, New trust level of the user
Add Users to Group · Read

Add users to a group

add_users_to_group · Risk: low · Retry: safe

Inputs

  • group_id · string · Required, Id of the group
  • users · array · Required, List of users to add to the group
Send Private Message · Read

Send a private message in Discourse

send_private_message · Risk: low · Retry: safe

Inputs

  • title · string · Required, Title for the PM
  • raw · string · Required, Content of the post
  • target_recipients · array · Required, List of users to send the PM to (can be one or more)
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Discourse 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:
  • API Key (api_key), required; stored as a sensitive connection value.
  • API Username (api_username), required.
  • Website URL (website_url), required.
  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-discourse@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 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.
  • 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 Discourse 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-discourse@0.2.0 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