Overview
Connect Thankster with Flows360
Thankster integration for Flows360 workflows.
Use the Thankster 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 1 action and no declared triggers.
Available actions
- Send Cards
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: Thankster
- Package:
@activepieces/piece-thankster@0.1.7 - Exact artifact digest:
sha256:d8be0fe32c323ee751ff3340edf240876eb1c3ecc06aea7c0c5e5397a9eb8fa9 - 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
- Send Cards (
send_handwritten_cards), Automatically send handwritten cards. 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
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Send Cards | Yes | No | Automatically send handwritten cards. |
Supported actions
Send Cards · Read
Automatically send handwritten cards.
send_handwritten_cards · Risk: low · Retry: safe
Inputs
templateID· string · Required, If you are passing text or images from prior steps in this step into the Thankster template chosen above, be sure to select a template that has corresponding text or images boxes to pass it into. Either way, the font and style of your cards will be taken from the template you select.fname· string · Required, Sender first name.lname· string · Optional, Sender last name.company· string · Optional, Enter sender company name.address· string · Required, Enter sender address1.address2· string · Optional, Enter sender address2.city· string · Required, Enter sender city.state· string · Optional, Enter sender state.zip· string · Required, Enter sender zip.country· string · Optional, If not US, type the two character country code.r_fname· string · Required, Receiver first name.r_lname· string · Optional, Receiver last name.r_company· string · Optional, Receiver company name.r_address· string · Required, Receiver address1.r_address2· string · Optional, Receiver address2.r_city· string · Required, Receiver city.r_state· string · Optional, Receiver state.r_zip· string · Required, Receiver zip.r_country· string · Optional, If not US, type the two character country code.api_text_one· string · Optional, Optional - if left blank, it will take the message from your Thankster template. Otherwise, map this to an api text box in the Thankster template being in Thankster Template field, 200 character maximum suggested.api_text_two· string · Optional, Optional - if left blank, it will take the message from your Thankster template. Otherwise, map this to an api text box in the Thankster template being in Thankster Template field, 200 character maximum suggested.api_text_three· string · Optional, Optional - if left blank, it will take the message from your Thankster template. Otherwise, map this to an api text box in the Thankster template being in Thankster Template field, 200 character maximum suggested.api_text_four· string · Optional, Optional - if left blank, it will take the message from your Thankster template. Otherwise, map this to an api text box in the Thankster template being in Thankster Template field, 200 character maximum suggested.api_image_one· string · Optional, Optional image URL for image one. Be sure this image is at least 1500 x 1900 pixels and has that aspect ratio to avoid stretching or pixelated.api_image_two· string · Optional, Optional image URL for image one. Be sure this image is at least 1500 x 1900 pixels and has that aspect ratio to avoid stretching or pixelated.api_image_three· string · Optional, Optional image URL for image one. Be sure this image is at least 1500 x 1900 pixels and has that aspect ratio to avoid stretching or pixelated.api_image_four· string · Optional, Optional image URL for image one. Be sure this image is at least 1500 x 1900 pixels and has that aspect ratio to avoid stretching or pixelated.sender_image· string · Optional, Optional image URL for return address (on the envelope). The recommended image size is 300x120 pixels or that aspect ratio to avoid stretching or pixelation. The image will be on top of the text and it will be downsized preserving the aspect ratio to fit the boundaries if necessary.recipient_image· string · Optional, Optional image URL for return address (on the envelope). The recommended image size is 300x120 pixels or that aspect ratio to avoid stretching or pixelation. The image will be on top of the text and it will be downsized preserving the aspect ratio to fit the boundaries if necessary.
Setup
Setup
- Add the Thankster connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-thankster@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 1 action 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 Thankster 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-thankster@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.