Pylon Reply
CertifiedReply to a Pylon issue
Pylon Reply
Reply to a Pylon issue
Calls POST /issues/{id}/reply to send a customer-facing reply, visible to the requester. messageId must be the top-level id of an existing customer-visible message on the issue (from the Pylon GET /issues/{id}/messages endpoint) — it selects which conversation or thread the reply is delivered on and, for email, controls the reply-chain headers.
type: io.kestra.plugin.pylon.issue.ReplyExamples
Reply to a Pylon issue
id: reply_pylon_issue
namespace: company.team
inputs:
- id: issue_id
type: STRING
- id: message_id
type: STRING
description: The top-level message ID from `GET /issues/{id}/messages` to reply to.
tasks:
- id: reply_issue
type: io.kestra.plugin.pylon.issue.Reply
apiToken: "{{ secret('PYLON_API_TOKEN') }}"
issueId: "{{ inputs.issue_id }}"
messageId: "{{ inputs.message_id }}"
bodyHtml: "We're looking into this, thanks for your patience!"
Properties
apiToken *string
Pylon API token
API token created by a Pylon Admin user (Pylon Settings > API), sent as Authorization: Bearer <token> on every request. Store it as a Kestra secret and reference it with {{ secret('PYLON_API_TOKEN') }} — never hardcode it in a flow.
bodyHtml *string
Reply body (HTML)
HTML content of the reply.
issueId *string
Issue ID or number
The Pylon issue to reply to.
messageId *string
Message ID
The top-level Pylon message ID to reply to, from the id field returned by GET /issues/{id}/messages. Must be customer-visible and belong to issueId.
assets
Assets this task consumes as inputs or produces as outputs, for lineage tracking and the asset graph (Enterprise Edition). A flow declaring this property on a task is rejected in the open-source edition.
io.kestra.core.models.assets.AssetsDeclaration
IGNOREFAILWARNAsset failure behavior
Behavior applied to the task state when a declared asset fails to render, emit, or be persisted (e.g. a lock conflict): FAIL escalates it to FAILED, WARN (default) warns it if it would otherwise succeed, IGNORE leaves the state untouched.
Whether to auto-register assets referenced dynamically at runtime that are not statically declared in inputs or outputs.
The assets consumed as inputs.
io.kestra.core.models.assets.AssetIdentifier
1The assets produced as outputs.
io.kestra.plugin.ee.assets.Dataset
1150{}1150io.kestra.plugin.ee.assets.File
1150{}1150io.kestra.plugin.ee.assets.Table
1150{}1150io.kestra.plugin.ee.assets.VM
1150{}1150io.kestra.core.models.assets.External
1150{}1150io.kestra.core.models.assets.Custom
11501Custom asset type
{}1150attachmentUrls array
Attachment URLs
URLs of files to attach to this reply.
baseUrl string
https://api.usepylon.comPylon API base URL
Base URL of the Pylon API. Defaults to the US region (https://api.usepylon.com); override with https://api.eu.usepylon.com for the EU region.
contactId string
Contact ID
Contact to post the reply as. Only one of userId/contactId may be set.
userId string
User ID
Pylon user to post the reply as. Only one of userId/contactId may be set.
Outputs
issueId string
Issue ID
Identifier of the issue the reply was posted on.
messageId string
Message ID
Pylon-assigned identifier of the newly created reply message.
