Integrating Hubspot with Document360

Prev Next

Plans supporting integration of Zapier extensions with Document360

Professional
Business
Enterprise






Many organizations around the world need a business automation tool that allows business promotions and manages marketing efforts by controlling sales processes. One such platform is Hubspot, a leading inbound marketing, sales, CRM, and customer success growth stack.


Integrating Hubspot with Document360

Using Document360 as your knowledge base platform and Hubspot for managing customer support tickets, you may encounter a need to automatically check if a related article exists in your internal knowledge base whenever a new support ticket is created in Hubspot. If no related article is found, a new knowledge base article can be created to address the knowledge gap and assist in resolving the support ticket efficiently.

To establish a connection between Hubspot and Document360, follow the below steps:

  1. Ensure that you have logged into your Zapier account.

  2. From the left navigation menu, click Create and then click Zaps from the options available.

  3. Zap will be created with Trigger and Action flow.

Connecting Hubspot and Document360 in Zapier

To establish a connection between Hubspot and Document360, follow the below steps:

Step 1: Connecting Hubspot

  1. In the Trigger field, choose Hubspot.

  2. In the Trigger event field, select the required Event to trigger in the Hubspot.

    If you wish to configure a different app later, you can do that by clicking on Change.

  3. Click the Account field, and a Sign-in panel will appear.

  4. Enter your sign-in credentials and select the checkbox.

  5. Click Connect app.

    Zapier runs a test to make sure the trigger is correctly configured.

  6. Click Continue.

Step 2: Connecting Document360

  1. In the Action field, choose Document360.

  2. On the Setup panel that appears on the right, select a desired event in the Event field.

  3. Click the Account field and a Sign-in panel appears.

  4. Enter your sign-in credentials and click Allow.


    To generate the API token from the Document360 portal,

  5. Navigate to Settings() > Knowledge base portal > Extensions > Team collaboration.

  6. On the Zapier extension tile, click Connect.

  7. Click the Copy () icon to copy the token.

  8. Head back to the Zapier panel and paste the API token in the field.

  9. Click Yes, Continue to Document360.

4_Screenshot_Zapier_API_Token_Pasting2

You can find the connected Document360 project on the Connect Document360 account page.

  1. Click Continue.

Step 3: Customize Zap

  1. Map all the required fields:

    • Ticket name: By default the ticket name will be set to ‘Title in Document360.’

    • Ticket description: By default the ticket description will be set to ‘Content in Document360.’

  2. Version: Select the workspace in your knowledge base project where the article should be created.

  3. Language: Choose the language for the article within the selected workspace.

  4. Should this step be considered a "success" when nothing is found?: Set to True or False.

  5. Once done, click Continue.

  6. Click Test & Continue.

Turn on Zap

To turn on a Zap once it is tested and published, follow the below steps:

  1. After testing the Zap, review or edit the settings before turning on the Zap.

  2. You can edit the settings configured on the Hubspot trigger and the corresponding action of the new article in Document360.

  3. You would get a success message stating Your Zap is on. You can click on the Manage your Zap button to go to your Zap overview page.


Zap overview

Create articles in Document360 from new support tickets in Hubspot

You can view and edit the information about the Zaps created on the Zap overview page.

Deleting a Zap

To delete a Zap that you have created,

  1. Navigate to the Zapier dashboard. On the overview page, a list of all existing Zaps will be displayed.

  2. Click the Zap actions () icon to the right of the desired Zap and click Delete.

    The selected Zap will be deleted.