Skip to main content
Clix currently exposes four built-in A2A skills. For production integrations, always specify the skill explicitly in a data part.

Canonical Request Pattern

Clix can infer a skill from text-only requests, but that routing is best-effort. Use data.skill when correctness matters.

Skill Summary

create-user

Creates or updates a user and writes a user-result artifact.

Parameters

Artifact

track-event

Tracks one event for one device and writes an event-result artifact.

Parameters

Artifact

send-push-notification

Sends one push notification request and writes a delivery-results artifact.

Parameters

At least one of deviceId, userId, or projectUserId must be present.

Artifact

results[].status is the raw delivery result enum string produced by Clix, such as DELIVERY_RESULT_STATUS_SUCCEED or DELIVERY_RESULT_STATUS_FAILED.

trigger-campaign

Creates a trigger for an existing campaign and writes a trigger-result artifact.

Parameters

targets can be omitted or empty. In that case, Clix creates the trigger without an explicit target list.

Artifact

Example Payloads

create-user

track-event

send-push-notification

trigger-campaign