Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Weekdone

OKR & weekly status reporting tool for teams.

CategoryProductivity
AuthenticationOAuth 2.0
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Weekdone with Flows360

OKR & weekly status reporting tool for teams.

Use the Weekdone 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 5 actions and 2 triggers.

Available actions

  • Create New Item
  • Update Item
  • Create New Objective
  • Update Objective
  • Custom API Call

Available triggers

  • New Item
  • New Objective

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: Weekdone
  • Package: @activepieces/piece-weekdone@0.1.0
  • Exact artifact digest: sha256:a1bb8af64450900aca85f634ff26a17d7ce77f28a69b2a581ff47f3b8ae0e146
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. 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 New Item (create_item), Creates a new report item in Weekdone. Classification: read.
  • Update Item (update_item), Updates an existing report item in Weekdone. Classification: read.
  • Create New Objective (create_objective), Creates a new OKR objective in Weekdone. Classification: read.
  • Update Objective (update_objective), Updates the description of an existing OKR objective in Weekdone. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Item, polling.
  • New Objective, polling.

Verification

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

Capability summary

AuthenticationOAuth 2.0
Supported objects7
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Create New Item Yes No Creates a new report item in Weekdone.
Update Item Yes No Updates an existing report item in Weekdone.
Create New Objective Yes No Creates a new OKR objective in Weekdone.
Update Objective Yes No Updates the description of an existing OKR objective in Weekdone.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Item Yes No polling trigger declared by the pinned package.
New Objective Yes No polling trigger declared by the pinned package.

Setup

Setup

  1. Add the Weekdone 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-weekdone@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 2 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 Weekdone 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-weekdone@0.1.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