Class RawVisitorsClient


  • public class RawVisitorsClient
    extends java.lang.Object
    • Constructor Detail

      • RawVisitorsClient

        public RawVisitorsClient​(ClientOptions clientOptions)
    • Method Detail

      • updateVisitor

        public IntercomHttpResponse<java.util.Optional<Visitor>> updateVisitor​(java.lang.Object request)
        Sending a PUT request to /visitors will result in an update of an existing Visitor.

        Option 1. You can update a visitor by passing in the user_id of the visitor in the Request body.

        Option 2. You can update a visitor by passing in the id of the visitor in the Request body.

      • updateVisitor

        public IntercomHttpResponse<java.util.Optional<Visitor>> updateVisitor​(java.lang.Object request,
                                                                               RequestOptions requestOptions)
        Sending a PUT request to /visitors will result in an update of an existing Visitor.

        Option 1. You can update a visitor by passing in the user_id of the visitor in the Request body.

        Option 2. You can update a visitor by passing in the id of the visitor in the Request body.

      • convertVisitor

        public IntercomHttpResponse<Contact> convertVisitor​(ConvertVisitorRequest request)
        You can merge a Visitor to a Contact of role type lead or user.

        📘 What happens upon a visitor being converted?

        If the User exists, then the Visitor will be merged into it, the Visitor deleted and the User returned. If the User does not exist, the Visitor will be converted to a User, with the User identifiers replacing it's Visitor identifiers.

      • convertVisitor

        public IntercomHttpResponse<Contact> convertVisitor​(ConvertVisitorRequest request,
                                                            RequestOptions requestOptions)
        You can merge a Visitor to a Contact of role type lead or user.

        📘 What happens upon a visitor being converted?

        If the User exists, then the Visitor will be merged into it, the Visitor deleted and the User returned. If the User does not exist, the Visitor will be converted to a User, with the User identifiers replacing it's Visitor identifiers.