Pylon Create
CertifiedCreate a Pylon issue
Pylon Create
Create a Pylon issue
Calls POST /issues to create a new issue and its first message. Requires either accountId or requesterEmail so Pylon knows which customer the issue is for.
type: io.kestra.plugin.pylon.issue.CreateExamples
Create a Pylon issue from a flow
id: create_pylon_issue
namespace: company.team
inputs:
- id: subject
type: STRING
- id: description
type: STRING
tasks:
- id: create_issue
type: io.kestra.plugin.pylon.issue.Create
apiToken: "{{ secret('PYLON_API_TOKEN') }}"
title: "{{ inputs.subject }}"
bodyHtml: "{{ inputs.description }}"
requesterEmail: "customer@example.com"
- id: log_issue_url
type: io.kestra.plugin.core.log.Log
message: "Created Pylon issue: {{ outputs.create_issue.issueUrl }}"
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
Issue body (HTML)
HTML content of the issue's first message.
title *string
Issue title
Short summary of the issue shown in Pylon.
accountId string
Account ID
Pylon account this issue belongs to. Required unless requesterEmail (or a requester) is provided.
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
{}1150assigneeId string
Assignee ID
Pylon user ID the issue should be assigned to.
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.
customFields object
Custom fields
Map of custom field slug to value. Use a list value for a multi-valued field (e.g. multiselect), or a single string otherwise. Field slugs are listed by the Pylon GET /custom-fields endpoint.
priority string
URGENTHIGHMEDIUMLOWPriority
Priority of the issue. Leave blank to use Pylon's default.
requesterEmail string
Requester email
Email of the customer this issue is for. If no matching contact exists, one is created. Required unless accountId is provided.
teamId string
Team ID
Pylon team the issue should be assigned to.
Outputs
issue object
Issue
Full Pylon issue object as returned by the API.
issueId string
Issue ID
Pylon-assigned identifier of the newly created issue.
issueNumber integer
Issue number
Human-readable issue number, taken from the response's number field. Null if the field is missing or not numeric.
issueUrl string
Issue URL
Link to the issue in Pylon, taken from the response's link field. Null if the API response omits it.
