Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Senja

Collect, manage, and share testimonials with Senja.

CategoryMarketing
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Senja with Flows360

Collect, manage, and share testimonials with Senja.

Use the Senja 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 11 actions and 1 trigger.

Available actions

  • List Testimonials
  • Get Testimonial
  • Create Testimonial
  • Update Testimonial
  • Delete Testimonial
  • Find Testimonials
  • Fetch Testimonial
  • Add Testimonial
  • Plus 3 additional declared actions.

Available triggers

  • Testimonial Event

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: Senja
  • Package: @activepieces/piece-senja@0.2.0
  • Exact artifact digest: sha256:a24732b5fffd6cebe83caa984480f08e11b64b229f6703cfa06d14ca3e406787
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • List Testimonials (list_testimonials), Retrieve all testimonials from your Senja project. Classification: read.
  • Get Testimonial (get_testimonial), Retrieve a specific testimonial by its ID. Classification: read.
  • Create Testimonial (create_testimonial), Add a new testimonial to your Senja project. Classification: read.
  • Update Testimonial (update_testimonial), Approve, unapprove, or update tags on an existing testimonial. Classification: read.
  • Delete Testimonial (delete_testimonial), Permanently delete a testimonial from your Senja project. This action cannot be undone. Classification: read.
  • Find Testimonials (find_testimonials), Search and list testimonials from your Senja project. Classification: read.
  • Fetch Testimonial (fetch_testimonial), Retrieve a specific testimonial by its ID. Classification: read.
  • Add Testimonial (add_testimonial), Add a new testimonial to your Senja project. Classification: read.
  • Modify Testimonial (modify_testimonial), Approve, unapprove, or update tags on an existing testimonial. Classification: read.
  • Remove Testimonial (remove_testimonial), Permanently delete a testimonial from your Senja project. This action cannot be undone. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Testimonial Event, 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 objects12
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Testimonials Yes No Retrieve all testimonials from your Senja project.
Get Testimonial Yes No Retrieve a specific testimonial by its ID.
Create Testimonial Yes No Add a new testimonial to your Senja project.
Update Testimonial Yes No Approve, unapprove, or update tags on an existing testimonial.
Delete Testimonial Yes No Permanently delete a testimonial from your Senja project. This action cannot be undone.
Find Testimonials Yes No Search and list testimonials from your Senja project.
Fetch Testimonial Yes No Retrieve a specific testimonial by its ID.
Add Testimonial Yes No Add a new testimonial to your Senja project.
Modify Testimonial Yes No Approve, unapprove, or update tags on an existing testimonial.
Remove Testimonial Yes No Permanently delete a testimonial from your Senja project. This action cannot be undone.
Custom API Call Yes No Make a custom API call to a specific endpoint
Testimonial Event Yes No webhook trigger declared by the pinned package.

Triggers

Testimonial Event · Webhook

Triggers when a testimonial is created, updated, or deleted in Senja.

Inputs

  • instructions · string
  • events · array

Setup

Setup

  1. Add the Senja 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:
  • No provider credential fields are declared by the pinned package.
  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-senja@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 1 trigger 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 Senja 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-senja@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