Connect Parseur to Amplitude

Both apps 28Parseur 16Amplitude 12

• 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
  Batch upload events

  Sends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.

• Action
  Export event data

  Exports every event Amplitude recorded in a time window, as a zip archive of event data.

• Action
  Get cohort

  Returns one behavioral cohort's details, including its name, size and when it was last recalculated.

• Action
  Get event segmentation

  Counts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.

• Action
  Get funnel analysis

  Runs a funnel over a series of events and returns how many users reached each step and how many dropped off.

• Action
  Get retention analysis

  Shows how many users came back and did something again after a starting event, over a date range.

• Action
  Get user properties

  Looks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.

• Action
  Group identify

  Sets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.

• Action
  Identify user

  Sets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.

• Action
  List cohorts

  Lists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.

• Action
  Send event

  Records a single event in Amplitude for a user, with optional event and user properties.

• Action
  Upload cohort

  Creates a cohort in Amplitude from a list of users you supply.

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