# Unifygtm > ## Documentation Index --- # Source: https://docs.unifygtm.com/reference/integrations/6sense.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # 6sense Integration Guide > Use your existing subscription to identify website visitors. # Overview Unify integrates with 6sense in two ways: * If you already have a 6sense subscription, you can connect it to Unify by providing your API key to identify website visitors. * [Unify Intent](https://app.unifygtm.com/dashboard/settings/integrations/unify-intent) identifies website visitors out of the box and is powered by 6sense as well as other providers. Unify uses 6sense along with various other providers to identify website visitors. If you already have a 6sense subscription, you can connect it to Unify by providing your API key. # Setup To connect your existing 6sense subscription to Unify, simply navigate to [Settings -> Integrations -> 6sense](https://app.unifygtm.com/dashboard/settings/integrations/6sense) and enter your API key. Unify will start using your 6sense account to identify website visitors. Some customers do not have their 6sense API token enabled by default. If you don't see website visitors being identified soon after entering your API key and setting up the website tag, this might be the case for you. You can reach out to [support@6sense.com](mailto:support@6sense.com) or your dedicated CSM with the following message: > Hi there, > > We need an API token to hit the reveal ([https://epsilon.6sense.com/v3/company/details](https://epsilon.6sense.com/v3/company/details)) API in a server to server (not from the browser) mode. > > Could you please provide the API key? > > Thanks, They should be able to enable access for you. --- # Source: https://docs.unifygtm.com/reference/plays/actions.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # Play Actions > Actions are the building blocks of Unify Plays. ## Overview Plays chain together actions to perform anything from simple automations to complex and dynamic outbound campaigns. Below are the actions you can choose from when creating a Play. ## Core actions ### AI qualification AI agents are powerful tools for researching companies or people and answering questions about them. In Plays, the answers provided by an agent can be used to determine whether a company or person is qualified or not. When you select the agent qualification action, you will be able to choose an existing agent or create a new one. Every agent has a set of questions that it will answer about the given record. In the action configuration panel, you can select which answers are required for the record to be considered qualified. ### Assign owner The owner assignment action allows you to assign a record to a specific owner in Unify. Every company and person record in Unify has an owner, and this action allows you to set or change the owner of a record. When you connect a CRM to Unify, the owner of the corresponding records in the CRM will be synced into Unify. For records that don't yet have an owner or don't yet exist in the CRM, you can use this action to assign an owner. You can also choose to update the owner if desired. ### Prospect One of the most common use cases for Plays is to find new people to reach out to. The prospecting action takes a company record as input and finds new people at the company matching specific personas and criteria. When you select the prospecting action, you can specify one or more personas to search for. The personas are considered in order, so the first persona will be preferred over the second, and so on. You can also specify a limit on the number of people to find per company. If the **Include existing people** option is enabled, existing people at the company already in Unify will count towards this limit. This can be useful if you want to save prospecting credits on companies you already have relevant contacts for. ### Sequence The sequence enrollment action makes building automated outbound campaigns easier than ever. You can choose which sequences to send people to based on which personas they match. The routing configuration provides a way to specify which mailboxes and sequences should be used for people this action runs on. You can specify a set of mailboxes to use or choose to use a mailbox associated with the [company or person record owner](/reference/plays/actions#assign-owner-action). You also have the option to set a limit on how many people to enroll per company, which is generally recommended to avoid overtargeting a single company. This limit applies globally across play runs, so if multiple Plays run on the same company, this limit will be shared across all of them. ### Slack alert The Slack alert action allows you to send a customized Slack message at any point in a Play. You can send messages to any public channels or DM any users in your workspace. The contents of the messages can be customized with template variables, so you can include information about the record that triggered the action. If the value for a template variable is missing, the message will still be sent, but the variable will be replaced with `Unknown`. You may optionally tag the owner of the account (e.g. `@John Doe`), so they can be easily notified of the alert. You can also include intent signal information containing recent website visitors, G2 page views, and more. This action is available when Slack connected to Unify. See the [Slack Integration Guide](/reference/integrations/slack) for information on integrating Slack with Unify. ### Sync to HubSpot The HubSpot sync action allows you to create or update a record in HubSpot based on a company or person record in Unify. This action will use the settings you've configured for HubSpot in the Unify settings. You also have the option to specify additional default field values. These will be written to HubSpot unless a different Unify field is already mapped to the HubSpot field. ### Sync to Salesforce The Salesforce sync action allows you to create or update a record in Salesforce based on a company or person record in Unify. This action will use the settings you've configured for Salesforce in the Unify settings. You also have the option to specify additional default field values. These will be written to Salesforce unless a different Unify field is already mapped to the Salesforce field. ## Utility actions ### Loop In order to fully understand the purpose of loops and how to use them effectively, it's recommended that you read about action [inputs and outputs](/reference/plays/building-a-play#inputs-and-outputs) first. Most actions run on one record at a time. Loops are a simple way to run one or more actions on every record in a list. For example, a **Prospect for new People** action will return a list of people. You can connect a loop action to the prospecting action and then add actions within the loop. The first action in the loop will receive one person at a time. ### If / Else The if-else action creates a branch in a Play, evaluates some conditions for records, and sends them down a specific path based on the result. This allows you to perform different actions on different records based on criteria that you specify. This action enables you to solve a wide variety of more complex use cases using Plays. For example, you can enroll people into different sequences based on their company firmographics, exact job title, or custom CRM field values. ### A/B Test The A/B test action allows you to route records down a specific path based on a set probability. This is useful for testing different sequences or actions. ### Delay The Delay action waits for a specified amount of time before continuing to the next action in a Play. This can be useful for spacing out actions in a Play and ensuring that actions are performed at the right time. This action is particularly useful when combined with if-else actions. For example, when a person visitors your website, it can be useful to wait a few minutes before taking action to see which pages they end up visitor or whether they fill out a form. ### Get Company If you have a person record, you can use this action to fetch the company that the person works at. If the person does not have a company associated with them, this action will not return any result. ### Get People If you have a company record, you can use this action to fetch people that work at the company. Unlike the **Prospect for new People** action, this action only looks for people that already exist in Unify rather than prspect for new people. ## Coming soon There are lots of additional actions in the works including more powerful AI features and deep integrations with third-party tools. If you're interested in an action that isn't available yet, [let us know](mailto:support@unifygtm.com)! We'll get you in the beta as soon as it's ready. --- # Source: https://docs.unifygtm.com/reference/management/authentication.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # Authentication Options > Learn about the login methods available for your organization in Unify. ## Overview Unify supports the following forms of authentication: 1. **Username and Password**: Users can log in with an email address and password managed by Unify. 2. **Google Workspace**: Users can log in using a Google account associated with your organization's Google Workspace. 3. **Single Sign-On (SSO) via SAML 2.0**: Unify supports SSO through the SAML 2.0 protocol. This allows your organization to use your existing identity provider (IdP), such as Okta or Azure AD, to authenticate your users. All methods are powered by Auth0, the leading industry standard for secure authentication. ### Single Sign-On (SSO) Our team will work directly with you to integrate Unify with your identify provider. Below are the steps and information we'll cover during this process. Unify does charge an SSO fee which is a direct passthrough cost from our provider. #### Supported Identity Providers (IdPs) * Okta * Azure Active Directory (AD) * Any SAML 2.0 compliant IdP #### Information required for SSO setup * **Sign In URL**: The URL where SAML authentication requests are sent. This is also called the single sign-on (SSO) endpoint. * **Sign Out URL**: The URL where SAML logout requests are sent. This is also called the single logout (SLO) endpoint. * **X.509 Certificate**: A certificate used to verify the SAML response. --- # Source: https://docs.unifygtm.com/reference/integrations/salesforce/bidirectional-syncs.md # Source: https://docs.unifygtm.com/reference/integrations/hubspot/bidirectional-syncs.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # How Bidirectional Syncs Work > An in-depth explanation of how syncs work between HubSpot and Unify. # Overview Unify can create and update HubSpot records in response to Play runs and sequence enrollments. This page summarizes the rules used to determine when and how to create or update records in HubSpot. # Overwriting data Unify takes a very conservative approach to overwriting existing HubSpot data in order to make data loss impossible. This approach is based around only a few simple rules: * **Creating new records:** When Unify is creating a new HubSpot record, it will fill in all properties that are enabled for writing in the field mapping or default values. * **Updating existing records:** Unify will inspect whether the field is empty or not. If the field already has a value, it will only be updated if it is a Unify-specific field. These fields are prefixed with "Unify" and can be found [here](/reference/integrations/hubspot/field-mappings#available-fields). These rules apply regardless of how the record was originally created (e.g., by Unify or externally). If you're looking for more fine-grained control, you can also limit the permissions granted to the Unify integration user in HubSpot. # Duplicate prevention Duplicates are strictly prevented within Unify. When creating new HubSpot records, Unify will only ever create one record. If there is already an existing HubSpot record of the same type, Unify will always update it rather than creating a new one. However, duplicates are a common problem in HubSpot and may already exist in your HubSpot instance. In addition, users or other integrations may accidentally create new duplicates over time. In order to accommodate this reality, Unify follows specific rules to ensure predictable behavior when updating duplicated HubSpot records. While Unify cannot de-duplicate your HubSpot, it will *never* make the problem worse, and in some situations may be able to help clarify the “source of truth” record. ### Contacts If there is an existing contact that matches the Unify person being written, it will be updated. Matches are determined based on email address. If there are no matches, a new contact will be created. If there are multiple contacts that match the Unify person, only one will be updated. Specifically, the contact that was most recently modified within HubSpot is the one that will be updated. ### Companies HubSpot companies are written by Unify whenever a contact is created or updated. They are also written if a HubSpot sync action runs within a Play that is running on companies. If there is an existing company that matches the Unify company being written, it will be updated. Matches are determined based on the domain of the company website. Domains are normalized, so URLs that redirect to different domains will not result in duplicates. If there are no matches, a new company will be created. If there are multiple companies that match the Unify company, only one will be updated. Specifically, the company that was most recently modified within HubSpot will be updated. ### Email Messages Unify does not update existing email messages in HubSpot; only emails sent through Unify or received in response to those emails will be written to HubSpot. Email messages are written to HubSpot for all emails sent as a part of Unify sequences if the corresponding person already exists in HubSpot. This means that in order to write email messages for sequence enrollments, you should ensure that the person already exists in HubSpot or that you include a Play action to sync them to HubSpot. --- # Source: https://docs.unifygtm.com/reference/plays/building-a-play.md > ## Documentation Index > Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt > Use this file to discover all available pages before exploring further. # Building a Play > Learn the fundamentals of creating Plays in Unify. export const PlayBuilderCompanyHandleDark = () => ; export const PlayBuilderCompanyHandleLight = () => ; export const PlayBuilderPersonListHandleDark = () => ; export const PlayBuilderPersonListHandleLight = () => ; export const PlayBuilderPersonHandleDark = () => ; export const PlayBuilderPersonHandleLight = () => ; ## Actions and triggers The building blocks of Plays are called *actions*. Each action is a different step of a Play, each representing a different task that can be automated in Unify. Every Play stars with a special type of action called a *trigger*. A trigger is the starting point of your Play which defines when the Play should be executed and what data should be provided to it. Here are a few of the triggers you can choose from: * **Record enters an Audience**: Run a Play once on every company or person that "enters" an Audience. Audiences can be reused across multiple Plays. * **Record matches criteria**: Run a Play once on every company or person that matches a set of filters. This trigger is similar to the audience trigger, but it doesn't require you to create a separate audience. Useful when you don't need to create a reusable audience. * **Manual**: Only run a Play when it is manually triggered. For example, you can send individual companies or people to a Play, or you can send an entire audience. Once the trigger is selected, you can start adding additional actions to the Play. Each action performs a different task. Actions can be chained together or perform branching logic based on the results of the previous action. Here are some of the most commonly used actions: * **AI Agent Qualification**: Perform AI-powered research to answer qualifying questions about a company or person. * **Prospect for new People**: Find new people at a company matching specific personas. You can specify a limit on the number of people to find. * **Sequence Enrollment**: Enroll a person in a sequence. You can route people to different mailboxes and sequences based on their persona. * **Write to Salesforce or HubSpot**: Sync a company or person to Salesforce or HubSpot. This will create or update a record in your CRM. You can find details about the full set of available triggers and actions in the reference sections below: See the full list of triggers available in Unify and how to use them. See the full list of actions available in Unify and how to use them. ## Inputs and outputs Each action receives an input and produces an output. Actions in the Play Builder have small colored symbols that represent what type of input and output they expect. Here's what each symbol represents: | Symbol | | Value | | :-------------------------------------------------------------------------: | - | :------------------------------------ | | {}{} | | A single person record. | | {}{} | | A list of one or more person records. | | {}{} | | A single company record. | Plays work by connecting each action's output to a matching input on another action. This is how data flows through the Play and how each action knows what to do. ## Connecting actions To connect two actions, click on the output symbol of the first action and drag the connection to the input symbol of the second action.