Connect Parseur to Loops

Both apps 27Parseur 16Loops 11

• 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 Contact

  Creates a new contact in your Loops audience, with optional name, user group, subscription status, mailing list memberships and custom contact properties.

• Action
  Add contact property

  Creates a new custom contact property in your Loops account, such as a plan name or signup date, so it can be stored on contacts.

• Action
  Delete Contact

  Deletes a contact from your Loops audience, identified by email address or user ID.

• Action
  Find Contact

  Finds a Loops contact by email address or by your own user ID and returns the matching contact, including its custom properties.

• Action
  Get campaign

  Returns a single Loops campaign by its ID, including its name, status, audience, mailing list and schedule.

• Action
  List campaigns

  Returns all campaigns in your Loops account, with each campaign's name, status, audience and scheduling details.

• Action
  List contact properties

  Returns the contact properties defined in your Loops account, either all of them or only your custom ones.

• Action
  List mailing lists

  Returns every mailing list in your Loops account, with each list's name, description and whether it is public.

• Action
  List transactional emails

  Returns the transactional emails in your Loops account, including each email's id, name, and the data variables it expects.

• Action
  Send Event

  Sends an event for a contact in Loops to trigger workflows, identifying the contact by email or user ID and optionally updating their contact properties and mailing list subscriptions.

• Action
  Update Contact

  Updates a Loops contact identified by email or user ID, including standard fields, custom contact properties and mailing list subscriptions. Creates the contact if no match exists.

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