Articles in this section

See more

How to Connect and Use ClientPoint with Zapier

Avatar
Elayza Cataluna
  • Updated
Follow

Overview: What is the ClientPoint Zapier Integration?

Put ClientPoint to work with AI and enterprise-grade automation.

Zapier is a no-code automation platform that acts as a bridge, connecting ClientPoint to over 8,000 other apps your team uses every day. This allows you to automate smarter, scale with confidence, and build powerful workflows without writing any code.

The integration is built for enterprise-grade security (SOC 2 and GDPR compliant) and provides an easy visual workflow builder to connect all your tools.

You can pair ClientPoint with all your critical apps, including:

  • HubSpot
  • Salesforce
  • Pipedrive & Pipeline CRM
  • monday.com
  • Airtable
  • ActiveCampaign
  • Gmail
  • Jotform

Getting Started: Connecting ClientPoint to Zapier

Before you can build a workflow (a "Zap"), you must connect your ClientPoint account to Zapier. This is done using a secure API key from your ClientPoint account.

  1. Log in to your Zapier account.
  2. Navigate to My Apps in the left-hand menu.
  3. Click the Add connection button.
  4. Search for "ClientPoint" and select it.
  5. A new window will pop up asking for your ClientPoint API Key.
  6. To find your API Key, log in to your ClientPoint account, navigate to Settings > My Profile > API Key.
  7. Copy your API Key from ClientPoint, paste it into the Zapier pop-up window, and click "Yes, Continue".

Your ClientPoint account is now connected and ready to use in any Zap.

Understanding ClientPoint Triggers

A Trigger is an event that happens in ClientPoint to automatically start your workflow. All ClientPoint triggers are Instant, meaning the Zap will run immediately after the event occurs.

Trigger: ClientPoint Created

  • Triggers when: A new ClientPoint is created.
  • When to Use: This is perfect for logging activity or kicking off a new process. You can use it to automatically create a new row in a Google Sheet for tracking, add a task to a project management tool, or log an activity in your CRM.
  • Setup:
    1. After you have chosen and tested your Trigger (the When this happens step), you set up the ClientPoint Action (the Then do this step).
    2. Search for the App: In the Action step, search for and select the ClientPoint app.
    3. Choose the Action Event: Select Create ClientPoint.
    4. Connect Account: Select your connected ClientPoint account. If you haven't connected it yet, follow the prompts to sign in using your API key.
    5. Click Continue.

Trigger: ClientPoint Updated

  • Triggers when: An existing ClientPoint is modified or updated.
  • When to Use: Use this to keep your other systems in sync. If a ClientPoint's name, value, or other details are changed, you can trigger a workflow to update the corresponding record in your CRM or project tool.
  • Setup:
    1. In the Trigger step, select the ClientPoint app.
    2. Choose the Trigger Event: ClientPoint Updated.
    3. Connect your account and test the trigger with a recently updated ClientPoint.

 Trigger: ClientPoint Approve 

  • Triggers when: A ClientPoint is marked as "Approved" (often used in an internal review workflow).
  • When to Use: This is ideal for multi-step workflows. When a manager approves a proposal inside ClientPoint, you can trigger a Zap to notify the sales rep in Slack, update the deal stage in your CRM to "Ready to Send," or create a task for the finance team.
  • Setup:
    1. In the Trigger step, select the ClientPoint app.
    2. Choose the Trigger Event: ClientPoint Approve.
    3. Connect your account and test the trigger. If no sample data is found, you may need to go into your ClientPoint account and formally approve a document to generate a test event.

Trigger: ClientPoint Signed

  • Triggers when: A document within a ClientPoint is successfully e-signed by a recipient.
  • When to Use: This is one of the most powerful triggers for automation. When a contract is signed, you can automatically:
    • Update the Opportunity in Salesforce or HubSpot to "Closed-Won."
    • Create a "DEAL WON! 🥳" message in a company Slack channel.
    • Create a new item in monday.com for the client onboarding team.
    • Archive the signed document to a specific folder in Google Drive.
  • Setup:
    1. In the Trigger step, select the ClientPoint app.
    2. Choose the Trigger Event: ClientPoint Signed.
    3. Connect your account and test the trigger with a recently signed ClientPoint.

Understanding ClientPoint Actions

An Action is an event your Zap performs inside ClientPoint after being triggered by an event in another app (e.g., your CRM, a form, or an email).

Create ClientPoint

  • The Goal: To automatically gather information from a trigger (like a new lead in a CRM) and use it to instantly generate a new ClientPoint.
  • Use Cases:
    • Automatically create a ClientPoint from a new Jotform submission.
    • Generate a ClientPoint when a deal in HubSpot reaches the "Proposal" stage.
  • Field Mapping:

Mapping the Fields (The Core Step)

This is the most important part. You will tell Zapier which piece of information from your Trigger app (e.g., your CRM or form) should go into each field of the new ClientPoint (refer to wiki).

🔴 Mandatory Fields (Required to Create the ClientPoint)

You must fill in these three fields by selecting data tags from your Trigger App's data or by typing in a static value.

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will use the sample data from your Trigger step and send it to ClientPoint to create a real proposal.
  4. Verify the Creation:
    - Log into your ClientPoint account and look for a new ClientPoint with the Name you mapped. 
    - If the test is successful, Zapier will show a green success message.

    Once the test is successful, click Publish Zap or Turn on Zap. 

 

Approve ClientPoint

  • The Goal: To automatically approve a specific ClientPoint when a condition is met (e.g., a manager marks a deal as "Ready for Approval" in your CRM).
  • Use Cases:
    • Auto-approve a ClientPoint based on a CRM stage change.
    • Trigger approval from an internal app or Slack command.
  • Field Mapping:

Mapping the Field (The Only Step)

This action requires only one piece of information: the unique ID of the ClientPoint you want to approve.

🔴 Mandatory Field (Required to Approve the ClientPoint)

You must fill in this field by mapping the ID from a previous step in your Zap (such as a 'Create ClientPoint' step or a step that searches your CRM for the ID).

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will send the approval command to ClientPoint for the ID you provided.

  4. Verify the Creation:
    - It should now be marked as Approved. The test will return a success message like this:



    Once the test is successful, click Publish Zap or Turn on Zap. 

     

ClientPoint Notes

  • The Goal: To automatically log important activities (like a client email or an internal update) onto an existing ClientPoint's activity feed.
  • Use Cases:
    • Log all email correspondence from Gmail as external notes.
    • Add internal comments from a Slack message or a Trello card.
  • Field Mapping:

Mapping the Fields (Adding the Note Details)

You must fill in all four fields below to successfully add a note.

🔴 Mandatory Fields (Required to Add the Note)

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will send the approval command to ClientPoint for the ID you provided.
  4. Verify the Creation:
    - Check the Notes/Activity section of the ClientPoint.
    - Your new note should be logged with the correct text and attributed to the mapped email address. The test will return a success message:

 

Once the test is successful, click Publish Zap or Turn on Zap. Your team's ClientPoints will now automatically log notes every time your Trigger event occurs!

 

Add Link (Embed)

  • The Goal: To automatically embed dynamic web content (like a product demo video or a third-party calculator) into a ClientPoint.
  • Use Cases:
    • Automatically add a unique Zoom meeting link after a meeting is booked.
    • Embed a link to a Google Drive folder or a specific resource URL.
  • Field Mapping:

Mapping the Fields (Defining the Content)

You must fill in all four required fields to successfully embed a link.

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will send the approval command to ClientPoint for the ID you provided.
  4. Verify the Creation:
    - Check the content list of the ClientPoint. You should see a new item with the File Name you provided, and clicking it should show the embedded webpage or video.
    - The test will return a success message similar to the sample data:

Once the test is successful, click Publish Zap or Turn on Zap. Your Zaps will now automatically add embedded links to your ClientPoints!

 

Document Generation

  • The Goal: To automatically generate a personalized document (like a contract or SOW) from a template and add it to an existing ClientPoint.
  • Use Cases:
    • Auto-generate a custom contract when a deal is moved to the "Contracting" stage.
    • Trigger a personalized quote document from a Jotform entry.
  • Field Mapping:

Mapping the Fields (The Customization Step)

You need to tell Zapier which ClientPoint to add the document to, which document template to use, and what data to use for personalization.

🔴 Mandatory Fields (Required for Generation)

  • Understanding JSON Data for Merge Fields:

    This step is for advanced users. If your document template in ClientPoint has placeholders like {{client_name}} or {{product_price}}, you can use this field to fill them in automatically.

    • Format: You must use strict JSON format: {"placeholder_name": "data_from_trigger"}

    • Example: If your document template has placeholders {{client_name}} and {{product_price}}, you would map the JSON Data field in Zapier by typing the following, and then replacing the text in ALL CAPS with the data tags from your trigger app:

      {"client_name": "Mapped Data: NAME OF CLIENT", "product_price": "Mapped Data: DEAL VALUE"}

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will send the approval command to ClientPoint for the ID you provided.
  4. Verify the Creation:
    - A new, generated document should appear in the content list.
    - If you provided JSON data, open the document to confirm that the merge fields (like {{client_name}}) have been replaced with the correct data.
    - The test will return a success message:

Once the test is successful, click Publish Zap or Turn on Zap. Your Zaps will now automatically generate personalized documents and add them to your ClientPoints!

 

Upload File

  • The Goal: To automatically upload an existing file (like a PDF, image, or signed contract from another source) to a specific ClientPoint.
  • Use Cases:
    • Attach a signed contract from a DocuSign trigger.
    • Upload client-provided files from a Google Drive folder.
  • Field Mapping:

Mapping the Fields (Defining the File)

You must fill in all five required fields to successfully upload the file.

🔴 Mandatory Fields (Required to Upload the File)

  • Test Your Action

Before turning your Zap on, you must test the action to ensure it works correctly.

  1. Click Continue after mapping all your fields.
  2. Click Test Action.
  3. Zapier will send the approval command to ClientPoint for the ID you provided.
  4. Verify the Creation:
    - Check the content list of the ClientPoint. You should see a new file with the File name you provided. The test will return a success message:

Once the test is successful, click Publish Zap or Turn on Zap. Your Zaps will now automatically upload files and documents to your ClientPoints!

 

Update ClientPoint

  • The Goal: To update fields on an existing ClientPoint, such as its Name, Revenue, or Expiration Date.
  • Use Cases:
    • If a deal's value is updated in your CRM, this action can automatically sync that new value to the ClientPoint.
    • Change the Assigned to email if a deal is reassigned to a new rep.
  • Field Mapping: This action will look similar to "Create ClientPoint," but you will first be required to map the ClientPoint ID of the one you wish to update.

Mapping the Fields (The Core Step)

The mapping is very similar to the "Create" action, but with one critical addition: the ClientPoint ID (refer to docs).

🔴 Mandatory Fields (Required to Update the ClientPoint)

You must fill in these four fields. Note that the Name, Revenue, and Assigned to Email are required even if they haven't changed, so you must map their current values.

Test Your Action

  • Click Continue after mapping all your fields.
  • Click Test Action.
  • Zapier will send the updated data to ClientPoint.

  • Verify the Update:
    - Log into your ClientPoint account and check the ClientPoint with the ID you provided.
    - Verify that the fields you mapped (like Revenue or Name) have been successfully changed.

    Once the test is successful, click Publish Zap or Turn on Zap. 

Troubleshooting & Best Practices

If your Zap is not working, check these common issues:

  • "Your Role does not support Oauth2 login...": This error occurs when the user's default NetSuite role does not have the correct permissions. Ensure all permissions assigned to the "Token Authentication Role" are also added to the user's default role.
  • ClientPoint Tab Not Visible in NetSuite: This can happen if the script deployment audience is not set correctly. In NetSuite, navigate to Setup > Script, find the script named "OIDC," and check its deployments. On the Audience tab, ensure the correct Departments, Subsidiaries, and Groups are assigned.
  • MFA (Multi-Factor Authentication) Issues: Users must set up their MFA authenticator app in NetSuite (Setup > Users/Roles > Manage Users) for the new token role to function correctly.
  • iFrame Not Loading in Safari: This is almost always caused by Safari's privacy settings. You must disable "Privacy > Prevent Cross-Site Tracking" to allow the ClientPoint iFrame to function correctly.
  • iFrame Shows NetSuite Login: This is often a browser cache issue. Clear your browser's cache and cookies, as old or invalid cookies from a previous session can interfere with the OIDC authentication flow.

For NetSuite Administrators: Rollback Instructions

If you need to revert back to the previous OAuth 1.0 SuiteBundle, follow these steps:

  1. Uninstall OAuth 2.0 SuiteBundle:
    • Log in to NetSuite as an Administrator.
    • Navigate to Customization > SuiteBundler > Search & Install Bundles.
    • Find the "ClientPoint for NetSuite" (OAuth 2.0) bundle in your list.
    • Click the gear icon and select Uninstall. Confirm the uninstallation.
  2. Search and Install OAuth 1.0 SuiteBundle:
    • After the uninstallation is complete, navigate back to Customization > SuiteBundler > Search & Install Bundles.
    • In the search bar, type your organization's name for the old OAuth 1.0 bundle (e.g., ClientPoint for NetSuite-OAuth1.0) and click Search.
    • Find the correct OAuth 1.0 bundle and click Install.
  3. Verify Installation:
    • After installation, check your "Installed Bundles" list to ensure it's active.
    • Navigate to an Opportunity record and verify that the ClientPoint tab is visible and functioning as expected under the OAuth 1.0 authentication.

      Have any questions? Please contact us at support@clientpoint.net

Related articles

Powered by Zendesk