Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Kudosity

Kudosity is a cloud-based SMS platform that enables businesses to send and receive text messages globally.

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Kudosity with Flows360

Kudosity is a cloud-based SMS platform that enables businesses to send and receive text messages globally.

Use the Kudosity 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 7 actions and 3 triggers.

Available actions

  • Add / Update Contact
  • Delete Contact
  • Cancel SMS
  • Format Number
  • Send SMS
  • Get SMS info
  • Custom API Call

Available triggers

  • Link Hit
  • SMS received
  • SMS Sent

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: Kudosity
  • Package: @activepieces/piece-kudosity@0.2.0
  • Exact artifact digest: sha256:8687f4597b49831b095f3bc26683bcb74118070e51e9033729c88a6bf12126dc
  • 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

  • Add / Update Contact (addUpdateContact), Create or update a list member in Kudosity Classification: read.
  • Delete Contact (deleteContact), Remove a list member from a Kudosity recipient list Classification: read.
  • Cancel SMS (cancelSms), Cancel a scheduled SMS message in Kudosity Classification: read.
  • Format Number (formatNumber), Format a phone number to international E.164 format Classification: read.
  • Send SMS (sendSms), Send an SMS message via Kudosity Classification: read.
  • Get SMS info (getSmsInfo), Retrieve details for a sent SMS by ID Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Link Hit, webhook.
  • SMS received, webhook.
  • SMS Sent, 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 objects10
Supported actions7
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add / Update Contact Yes No Create or update a list member in Kudosity
Delete Contact Yes No Remove a list member from a Kudosity recipient list
Cancel SMS Yes No Cancel a scheduled SMS message in Kudosity
Format Number Yes No Format a phone number to international E.164 format
Send SMS Yes No Send an SMS message via Kudosity
Get SMS info Yes No Retrieve details for a sent SMS by ID
Custom API Call Yes No Make a custom API call to a specific endpoint
Link Hit Yes No webhook trigger declared by the pinned package.
SMS received Yes No webhook trigger declared by the pinned package.
SMS Sent Yes No webhook trigger declared by the pinned package.

Supported actions

Add / Update Contact · Read

Create or update a list member in Kudosity

add_update_contact · Risk: low · Retry: safe

Inputs

  • listId · string · Required, Numeric ID of the recipient list (found in the list page URL).
  • msisdn · string · Required, Phone number with country code, e.g., +1234567890
  • email · string · Required
  • firstName · string · Optional
  • lastName · string · Optional
  • phone · string · Optional
  • customFields · object · Optional
Delete Contact · Read

Remove a list member from a Kudosity recipient list

delete_contact · Risk: low · Retry: safe

Inputs

  • listId · string · Optional, Numeric ID of the recipient list (found in the list page URL).
  • msisdn · string · Required, Phone number with country code (e.g., +1234567890)
Cancel SMS · Read

Cancel a scheduled SMS message in Kudosity

cancel_sms · Risk: low · Retry: safe

Inputs

  • id · string · Required, Numeric ID assigned to the message sent
Format Number · Read

Format a phone number to international E.164 format

format_number · Risk: low · Retry: safe

Inputs

  • country · string · Required, Country code or name (e.g., US, AU, NZ) to determine the number format
  • number · string · Required, Phone number in local format (spaces, hyphens, and other characters will be removed)
Send SMS · Read

Send an SMS message via Kudosity

send_sms · Risk: low · Retry: safe

Inputs

  • sender · string · Required, Sender number or alphanumeric sender that is assigned to your account
  • recipient · string · Required, Destination number (local or E.164 format)
  • message · string · Required, Body of the SMS message
  • messageRef · string · Optional, Optional reference string to correlate messages with your system
  • trackLinks · boolean · Optional, Enable link tracking for this message
Get SMS info · Read

Retrieve details for a sent SMS by ID

get_sms_info · Risk: low · Retry: safe

Inputs

  • id · string · Required, The message ID to retrieve (UUID returned when sending)
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Link Hit · Webhook

Triggered when a tracked link in a message is clicked

SMS received · Webhook

Triggered when an inbound SMS is received

SMS Sent · Webhook

Triggered when an SMS sent

Setup

Setup

  1. Add the Kudosity 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-kudosity@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 3 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 Kudosity 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-kudosity@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