Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Fragment

Fragment integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Fragment with Flows360

Fragment integration for Flows360 workflows.

Use the Fragment 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 2 triggers.

Available actions

  • Create Task
  • Update Task
  • Get Task
  • List Tasks
  • Delete Task
  • Custom API Call

Available triggers

  • New Task
  • Task Updated

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: Fragment
  • Package: @activepieces/piece-fragment@0.1.7
  • Exact artifact digest: sha256:1a4bd30d12402bc4594dfcef591d2741bd174887342b4e04d90c0cd981b38c35
  • 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

  • Create Task (create_task), Creates a new task in Fragment. Classification: read.
  • Update Task (update_task), Updates an existing task. Classification: read.
  • Get Task (get_task), Retrieves details of a specific task. Classification: read.
  • List Tasks (list_tasks), Retrieves a list of tasks from. Classification: read.
  • Delete Task (delete_task), Deletes an existing task. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to any Fragment endpoint Classification: read.

Trigger contracts

  • New Task, polling.
  • Task Updated, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects8
Supported actions6
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Task Yes No Creates a new task in Fragment.
Update Task Yes No Updates an existing task.
Get Task Yes No Retrieves details of a specific task.
List Tasks Yes No Retrieves a list of tasks from.
Delete Task Yes No Deletes an existing task.
Custom API Call Yes No Make a custom API call to any Fragment endpoint
New Task Yes No polling trigger declared by the pinned package.
Task Updated Yes No polling trigger declared by the pinned package.

Supported actions

Create Task · Read

Creates a new task in Fragment.

create_task · Risk: low · Retry: safe

Inputs

  • title · string · Required, The title of the task
  • url · string · Optional, A URL associated with the task (e.g., link to a ticket or resource)
  • due_at · string · Optional, When the task is due
  • assignee · string · Optional, Email of the person to assign this task to.
  • tags · array · Optional, Tags to categorize the task
  • custom_fields · object · Optional, Additional custom fields for the task
Update Task · Read

Updates an existing task.

update_task · Risk: low · Retry: safe

Inputs

  • task_uid · string · Required, The unique identifier of the task to update
  • title · string · Optional, The updated title of the task
  • url · string · Optional, The updated URL for the task
  • due_at · string · Optional, The updated due date
  • status · string · Optional, The status of the task
  • assignee · string · Optional, Email of the person to assign this task to
  • tags · array · Optional, Updated tags for the task
  • custom_fields · object · Optional, Updated custom fields
Get Task · Read

Retrieves details of a specific task.

get_task · Risk: low · Retry: safe

Inputs

  • task_uid · string · Required, The unique identifier of the task to retrieve
List Tasks · Read

Retrieves a list of tasks from.

list_tasks · Risk: low · Retry: safe

Inputs

  • status · string · Optional, Filter tasks by status
  • assignee · string · Optional, Filter tasks by assignee email or ID
  • limit · number · Optional, Maximum number of tasks to return (default: 50)
Delete Task · Read

Deletes an existing task.

delete_task · Risk: low · Retry: safe

Inputs

  • task_uid · string · Required, The unique identifier of the task to delete
Custom API Call · Read

Make a custom API call to any Fragment endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Required, Authorization headers are injected automatically from your connection.
  • queryParams · object · Required
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional
  • timeout · number · Optional
  • followRedirects · boolean · Optional

Triggers

New Task · Poll

Triggers when a new task is created.

Task Updated · Poll

Triggers when a task is updated.

Setup

Setup

  1. Add the Fragment 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-fragment@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 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 Fragment 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-fragment@0.1.7 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