​
What’s supported

​
Supported actions

This connector supports:
  • Read Actions, including full historic backfill. Please note that incremental read is supported only for issues currently. For all other objects, a full read of the Pylon instance will be done per scheduled read.
  • Write Actions.
  • Proxy Actions, using the base URL https://api.usepylon.com.
Important Note on Issues Backfill: The issues object has a 30-day limitation for historic backfill. To avoid timezone or timing issues, we recommend setting your backfill period to 29 days or less when syncing issues data.

​
Supported Objects

The Pylon connector supports reading from the following objects: The Pylon connector supports writing to the following objects:

​
Example integration

For an example manifest file of a Pylon integration, visit our samples repo on Github.

​
Using the connector

This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Pylon:
  • Create a manifest file like the example.
  • Deploy it using the amp CLI.
  • Embed the InstallIntegration UI component. The UI component will prompt the customer for their API Key.
  • Start making Read Actions, Write Actions, and Proxy Calls. Ampersand will automatically attach the required authentication headers supplied by the customer. Please note that this connector’s base URL is https://api.usepylon.com.

​
API documentation

For more detailed information about Pylon API, refer to the Pylon API documentation.