Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Date Helper

Manipulate, format, and extract time units for all your date and time needs.

CategoryCore
AuthenticationNo authentication required
Version0.1.34
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Date Helper with Flows360

Manipulate, format, and extract time units for all your date and time needs.

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

Available actions

  • Get Current Date
  • Format Date
  • Extract Date Units
  • Date Difference
  • Add/Subtract Time
  • Next Day of Week
  • Next Day of Year
  • First Day of Previous Month
  • Plus 1 additional declared action.

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: Date Helper
  • Package: @activepieces/piece-date-helper@0.1.34
  • Exact artifact digest: sha256:83f07e422aa40b24f641d260efb080d761c70bca532be4fbafe6d6e94f025885
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Current Date (get_current_date), Get the current date Classification: read.
  • Format Date (format_date), Converts a date from one format to another Classification: read.
  • Extract Date Units (extract_date_parts), Extract date units ( year , month , day , hour , minute , second , day of week , month name ) from a date Classification: read.
  • Date Difference (date_difference), Get the difference between two dates Classification: read.
  • Add/Subtract Time (add_subtract_date), Add or subtract time from a date Classification: read.
  • Next Day of Week (next_day_of_week), Get the date and time of the next day of the week Classification: read.
  • Next Day of Year (next_day_of_year), Get the date and time of the next day of the year Classification: read.
  • First Day of Previous Month (first_day_of_previous_month), Get the date and time of the first day of the previous month Classification: read.
  • Last Day of Previous Month (last_day_of_previous_month), Get the date and time of the last day of the previous month Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects9
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Get Current Date Yes No Get the current date
Format Date Yes No Converts a date from one format to another
Extract Date Units Yes No Extract date units ( year , month , day , hour , minute , second , day of week , month name ) from a date
Date Difference Yes No Get the difference between two dates
Add/Subtract Time Yes No Add or subtract time from a date
Next Day of Week Yes No Get the date and time of the next day of the week
Next Day of Year Yes No Get the date and time of the next day of the year
First Day of Previous Month Yes No Get the date and time of the first day of the previous month
Last Day of Previous Month Yes No Get the date and time of the last day of the previous month

Setup

Setup

  1. Add the Date Helper 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-date-helper@0.1.34; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 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 Date Helper 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-date-helper@0.1.34 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