Connect Chaport to Salesforce

Both apps 31Chaport 20Salesforce 11

• Trigger
  Chat Closed (instant)

  Fires when a chat is closed. Webhook event: chat.closed.

• Trigger
  Chat Finished

  Triggers when chat is finished.

• Trigger
  Chat Stage Updated (instant)

  Fires when a chat's stage changes. Webhook event: chat.stageUpdated.

• Trigger
  Message Read (instant)

  Fires when a message is read. Webhook event: message.read.

• Trigger
  New Chat Started

  Triggers when chat is started.

• Trigger
  New Message Sent (instant)

  Fires when a new message is sent in a chat. Webhook event: message.sent.

• Trigger
  New Visitor (instant)

  Fires when a new visitor is created. Webhook event: visitor.created.

• Trigger
  Visitor Updated

  Triggers when visitor data is updated.

• Action
  Create an Operator

  Adds a new operator to your Chaport account and returns the created operator.

• Action
  Delete a Message

  Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.

• Action
  Delete an Operator

  Removes an operator from your Chaport account.

• Action
  List Operators

  Returns every operator in your Chaport account, with each operator's name, email, role and status.

• Action
  List Visitors

  Returns the visitors in your Chaport account, one page at a time.

• Action
  Retrieve an Operator

  Returns one Chaport operator with their name, email, role, job title and current status.

• Action
  Retrieve a Visitor

  Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.

• Action
  Retrieve Last Visitor Chat

  Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.

• Action
  Send a Message

  Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.

• Action
  Update an Operator

  Updates a Chaport operator's details. Anything you leave blank keeps its current value.

• Action
  Update a Visitor

  Updates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.

• Action
  Update Operator Status

  Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.

• Trigger
  New object record

  Polling trigger: fires for each new record created in the specified SObject type. Polls SOQL ordered by CreatedDate descending.

• Trigger
  New or updated object record

  Polling trigger: fires for each record created or modified in the specified SObject type. Polls SOQL ordered by SystemModstamp descending.

• Action
  Create object record

  Creates a new record of the specified SObject type (standard or custom, e.g. Account, Contact, Lead, Opportunity, Case, or MyObject__c) with the supplied field values.

• Action
  Delete object record

  Deletes an existing SObject record by object type and record ID.

• Action
  Describe object

  Returns the full field and metadata description (describe) for an SObject type — useful for discovering available fields and their API names.

• Action
  Find most recent created or updated record

  Returns the single most recently created or last-modified record for the specified SObject type (ordered by SystemModstamp DESC, LIMIT 1).

• Action
  Find object records

  Finds matching records for an SObject type by a field/value equality match via SOQL. Returns Id and the requested fields for all matches.

• Action
  Get object record

  Retrieves a single SObject record by object type and record ID. Optionally restrict returned fields with a comma-separated 'fields' list.

• Action
  List objects

  Lists all available SObject types (standard and custom) on the org.

• Action
  SOQL query

  Executes a SOQL query against the org and returns matching records. Example: SELECT Id, Name FROM Account WHERE CreatedDate = TODAY.

• Action
  Update object record

  Updates an existing SObject record by object type and record ID with the supplied field values. Salesforce returns no body on success (HTTP 204).

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