Integrations and Customization | Hubspot

Introduction

The HubSpot Integrationmodule in CheckOp is an advanced functionality that allows synchronizing tasks between both platforms in a bidirectional way. This integration facilitates the flow of information, maximizing operational efficiency and real-time visibility of activities. It is crucial for teams that manage their customers and operations in different systems.

Synchronization Flows: The integration operates in both directions, allowing actions on one platform to be automatically reflected on the other.

Flows

HubSpot flow to CheckOp

  • Task (Ticket) Creation: A ticket created in HubSpot can automatically generate a task in CheckOp if the ticket moves to a predefinedstage or pipeline phase for integration (e.g., "Pending").

  • Edit Task (Ticket): Updates to a HubSpot ticket can modify the corresponding task in CheckOp.

CheckOp flow to HubSpot

  • Task Creation: A task created in CheckOp can generate a ticket or associated object record in HubSpot.
  • Task Execution Start: When a task in CheckOp changes status to "In Progress", the system automatically updates the stage of the corresponding ticket in HubSpot.
  • Task Execution Completion: When completing a task in CheckOp, the system updates the stage of the ticket in HubSpot to "Completed" or similar.

Functionalities and Components

  • Bidirectional CheckOp Integration with HubSpot (Tasks - Object HS): Enables synchronization of tasks with tickets, businesses or other HubSpot objects. In addition, key relationships can be established, such as linking the ticket owner with the assigned user in CheckOp and connecting with HubSpot contacts.

  • Synchronize HubSpot properties: The system can automatically create properties in HubSpot from fields in a CheckOp form. It is important that the data types are compatible (e.g., a CheckOp single selection field must match a property of the same type in HubSpot).

  • Manually set internal HubSpot Object property name: Allows to manually map CheckOp form fields to existing HubSpot properties, using the internal name of the property. This is useful if the customer already has a property structure defined.

  • Send CheckOp Report PDF File to HubSpot: The PDF report generated from a completed CheckOp task can be automatically sent to the corresponding ticket in HubSpot as an attachment, providing full document traceability.

  • Create notes on Task status changes: The system can generate automatic notes in the HubSpot ticket each time the status of a task in CheckOp changes (e.g., from pending to in progress, or upon reactivation), providing a detailed activity history.

Key Implementation Considerations

  • HubSpot Stages: Integration requires the configuration of at least three specific stages in a HubSpot pipeline (e.g., "Pending", "In Progress", "Completed") to synchronize the task lifecycle.

  • Integration Activation: Initial setup and integration activation with HubSpot is done at the development level, which means the CheckOp team must enable this option for the forms and entities you wish to sync.

  • Field Compatibility: CheckOp form media fields (photos, videos, voice memos, signatures, documents) do not sync directly with HubSpot.

  • Property Mapping: Synchronization of CheckOp properties to HubSpot works in two ways:

    1. Automatic Sync: CheckOp creates the properties in HubSpot.

    2. Manual Mapping: You can link CheckOp fields to existing HubSpot properties.

En esta página