Connect Parseur to Pylon

Both apps 41Parseur 16Pylon 25

• Trigger
  New Document Export Failed

  Triggered when Parseur fails to export a document to its destination.

• Trigger
  New Document Not Processed

  Triggered when Parseur receives a document it cannot extract data from, so you can follow it up.

• Trigger
  New Document Processed

  Triggered when Parseur finishes extracting data from a document, with the extracted fields.

• Trigger
  New Document Processed (With List Items)

  Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).

• Trigger
  New Mailbox

  Triggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.

• Trigger
  New Table Field Processed

  Triggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.

• Action
  Create Document

  Sends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.

• Action
  Create Document From File

  Uploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.

• Action
  Delete Document

  Deletes a document from Parseur by its ID.

• Action
  Delete Mailbox

  Deletes a Parseur mailbox and everything in it. This cannot be undone.

• Action
  Get Document

  Returns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.

• Action
  Get Mailbox

  Returns one Parseur mailbox by its ID, with its email address, document counts and settings.

• Action
  List Documents

  Returns the documents in Parseur, optionally narrowed to one mailbox or one processing status.

• Action
  List Mailboxes

  Returns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.

• Action
  Reprocess Document

  Sends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.

• Action
  Update Mailbox

  Updates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.

• Action
  Add internal note to issue

  Adds an internal note to a Pylon issue. Internal notes are not visible to the requester.

• Action
  Add tag

  Creates a new tag in Pylon that can be applied to accounts, articles or issues.

• Action
  Add task

  Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.

• Action
  Create Account

  Creates a new customer account in Pylon with its name, domains, owner, tags and other details.

• Action
  Create Account Activity

  Creates a custom activity on a Pylon account's timeline.

• Action
  Create Call Recording

  Creates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.

• Action
  Delete account

  Permanently deletes a Pylon account by its ID or external ID.

• Action
  Delete issue

  Permanently deletes an issue in Pylon.

• Action
  Find Account by Name

  Finds Pylon accounts by name, by exact or partial match, returning the matching accounts.

• Action
  Find contacts by criteria

  Returns the contacts that match the specified search text and/or filter.

• Action
  Find issues by criteria

  Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.

• Action
  Get account

  Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.

• Action
  Get contact

  Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.

• Action
  Get issue

  Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.

• Action
  Get user

  Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.

• Action
  Get Users

  Returns the users in your Pylon organization, optionally including deactivated users.

• Action
  List accounts

  Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.

• Action
  List contacts

  Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.

• Action
  List tags

  Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.

• Action
  List teams

  Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.

• Action
  Reply to issue

  Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.

• Action
  Update Account

  Updates an existing Pylon account. Only the fields you fill in are changed.

• Action
  Update contact

  Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.

• Action
  Update issue

  Updates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.

• Action
  Update Issue Followers

  Adds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.