Connect Bigin by Zoho CRM and Parseur

Both apps 52Bigin by Zoho CRM 36Parseur 16

• Trigger
  New Pipeline Record

  Triggers when a new pipeline record is created.

• Trigger
  New Task

  Triggers when a new task is added.

• Action
  Add note

  Adds a note to a Bigin contact, company, pipeline record, product, task, event or call.

• Action
  Add tags to record

  Add tags to a record.

• Action
  Create Call

  Adds a new call record (logged or scheduled call) in Bigin.

• Action
  Create Company

  Creates a new company

• Action
  Create Contact

  Creates a new contact.

• Action
  Create Event

  Creates a new event.

• Action
  Create or Update Company

  Creates a company in Bigin, or updates the existing company when one already matches on the company's unique fields (by default the company name).

• Action
  Create or Update Contact

  Creates a contact in Bigin, or updates the existing contact when one matches on the duplicate-check fields (such as email).

• Action
  Create or Update Pipeline Record

  Creates a pipeline record (deal) in Bigin, or updates the existing one that matches on its unique fields (the deal name by default).

• Action
  Create Pipeline Record

  Adds a new pipeline record (deal) to Bigin in the chosen sub-pipeline and stage.

• Action
  Create Product

  Creates a new product.

• Action
  Create Task

  Creates a new task.

• Action
  Delete company

  Deletes a company (Accounts module record) from Bigin.

• Action
  Delete contact

  Deletes a contact from Bigin by its ID.

• Action
  Delete pipeline record

  Deletes a pipeline record (deal) from Bigin by its ID.

• Action
  Delete task

  Deletes a task from Bigin by its ID.

• Action
  Get company

  Fetches a company by ID. An error occurs if the company is not found.

• Action
  Get contact

  Retrieves the full details of a single Bigin contact by its record ID, including any custom fields.

• Action
  Get pipeline record

  Retrieves one Bigin pipeline record (deal) by its ID, including its custom fields.

• Action
  Get Records Using COQL Query

  Runs a COQL SELECT query against a Bigin module (Contacts, Accounts, Pipelines, Products, Calls, Events, Tasks) and returns the matching records.

• Action
  Get Task

  Returns one Bigin task by its ID, with its subject, status, priority and owner.

• Action
  List Notes

  Returns the notes attached to a Bigin record, such as a company, contact or pipeline record.

• Action
  Search Company

  Returns the Bigin companies that match a search word, email address, phone number, or field criteria.

• Action
  Search Contact

  Returns the Bigin contacts that match a search word, email address, phone number or field criteria.

• Action
  Search Event

  Search Bigin events by a word, email, phone number or field criteria and return the matching events.

• Action
  Search Pipeline Record

  Returns the pipeline records (deals) that match a search word, email, phone number or field criteria.

• Action
  Search Product

  Returns the products that match a search word, email, phone number or field criteria.

• Action
  Search Task

  Searches Bigin tasks by word, email, phone or field criteria and returns the matches.

• Action
  Update Company

  Updates an existing company (Accounts module) in Bigin. Only the fields you fill in are changed.

• Action
  Update Contact

  Updates an existing contact in Bigin. Only the fields you fill in are changed; blank fields are left as they are.

• Action
  Update Event

  Updates an existing event

• Action
  Update Pipeline Record

  Updates an existing pipeline record (deal) in Bigin. Only the fields you fill in are changed.

• Action
  Update Product

  Updates an existing product in Bigin. Only the fields you fill in are changed.

• Action
  Update Task

  Updates a new task.

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

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