Salesforce Integration

Overview and Benefits

Note: This feature incurs additional fees.

This integration uses Calrizen's iHub application. To learn more about iHub, click here.

Clarizen's Salesforce integration enables sales and technical support teams to enhance their work process and account management capabilities by initiating and following Clarizen Projects, Cases, Users, and Discussions as well as other Clarizen objects within Salesforce. Additionally, Professional Service teams are able to view all relevant Salesforce information, custom or standard, directly in Clarizen.

The integration allows syncing objects between Salesforce and Clarizen. You can connect 2 Clarizen instances to Salesforce.

The integration includes a best practices package, which includes out-of-the-box mappings and triggers, allowing teams to get started with no additional setup.

Administrators can then configure their own mappings as needed for the customer's specific business needs.

This provides:

  • Superior Account Management — customer-facing executives can convert opportunities into projects more effectively by scoping and budgeting projects more accurately.
  • Real-time progress monitoring of customer and prospects related projects and cases, ensures communication of accurate and timely information flow.
  • Improved visibility of incoming projects, backlog and expected resourcing for Project and Delivery Teams.
  • Convenient creation and integration of new opportunities by Professional Services teams directly from Clarizen into Salesforce
  • Full synchronization between Salesforce Chatter and Clarizen discussions, allowing easy and open communication between team members regardless of where they are located.
    Note: Social posts and comments are synced between Clarizen and Chatter every 60 minutes.


  • You will need a Salesforce Enterprise Edition (EE) account
  • A Developer Account or a Sandbox account can be used to test the integration
  • Salesforce Professional Edition (PE) users need to use the previous Salesforce for Clarizen integration found here.

Salesforce integration provides several key benefits:

Sales automation

The following are just some of the key benefits relating to sales automation when integrating Salesforce with Clarizen:

  • Better forecasting capabilities with automatic creation of projects from opportunities
  • Allows professional services and customer success teams to view their upcoming pipeline, prioritize and make decisions that better impact the business bottom line
  • KPI measurement for success:
    • Resource utilization — Ensuring that the right people are staffed on the right projects bringing more projects to successful completion

Execution updates in sales tool

Keep track of the project execution with:

  • Real-time updates on project progress directly in Salesforce
  • Account executives can take action on customer updates and accounting
    • Full visibility into customer revenue recognition stream via milestones/work packages process and progress
  • KPI measurement for success: Customer satisfaction
    • Account executives gain visibility into project execution/onboarding progress and can react, thereby increasing customer satisfaction

Real-time team collaboration

Full collaboration between the different teams

  • Account executives and execution teams can seamlessly collaborate and react to changes in real-time
  • Professional services and customer success teams can instantly alert account executives to new opportunities based on past experiences
  • KPI measurement for success: Increase sales
    • Cross-system collaboration allows for improved sales operation with the added value of scoping out new opportunities

Setup Guide

To get more information about Clarizen integration with Salesforce, contact your account representative or email

Before you begin the integration process, contact your Success Manager and follow the instructions below.

Note: The current package version is 1.6

Initial Setup 

Key components of the integration:

  • Authentication
  • Mapping
  • Triggers
  • Sync schedule

This section explains the initial setup process for new customers, which includes the installation of the best practices package and out-of-the-box triggers and mappings.

Note: Make sure that you are logged in with a Salesforce Admin user during the setup and authentication process, as this user permission type is required for the integration to work properly.

  1. Install the Best Practices package before the setup by going to the Apps Marketplace.
    The Best Practices package installs default mappings and event triggers to get started quickly.
  2. In Clarizen, click on your username > Settings > Extensions.
  3. In the Connected Web apps section, click Open next to the Salesforce app.
  4. Click Login.
  5. In the Authorized Access screen, click Grant Access.
    Then click Login.
  6. You will now be redirected to your Salesforce login page, and after logging in you should see a message that the Best Practices package is being installed.
  7. The default mappings and events installed from the Best Practices package are now available in the Mappings & Events tab.

    The Events are disabled by default. To enable Events, select one or more and click Enable on the ribbon.
    The default events are triggered on Salesforce.
    Milestones are synced from Clarizen to Salesforce and not vice versa.

  8. In Salesforce, you will now be able to see Clarizen objects, however you may need to customize your layout to see the objects.

    In the Clarizen Integration Setup tab, you can see the same details as in the iHub application.
  9. Set up your Sync Schedule.
    The daily sync will sync all updated items in the sync registry up to twice a day.
    Go to Mappings & Events, and click Sync > Sync Schedule. Enter the two sync times.

    Once selected, the daily sync will create a scheduled workflow rule that does not use your quotas.
    Note: You may notice that some hours in the list are grayed out, this means that these times are already used by existing scheduled workflow rules in your Clarizen account(s) and cannot be selected.
    To sync selected items, click Sync Now.
  10. Set up additional mappings and event triggers as explained in Triggers and Mappings.

Working Example and Tips

The following example describes creating an Opportunity in Salesforce that creates a new Project in Clarizen.

  1. In Salesforce, click Create > Opportunity.
  2. Fill in the mandatory fields such as Opportunity Name and Account Name
  3. For the Stage option, select an option that raises the Probability to over 70%. This is because only a Probability of over 70% triggers the creation of the Project in Clarizen according to the Event trigger rule. 
  4. Save the new Opportunity and open it in Salesforce. Scroll down to see all its properties, where you can take actions. For example, you can add Products to the Opportunity. The Products will be created as Sub-Projects in Clarizen.
  5. Go to the Sync Registry, either via iHub or Salesforce. Note the newly created Project in Pending state. 
  6. A Success state appears when the sync is complete. You will also see the added Products (Sub-Projects) and Account (Customer).
  7. Click on the Project to Project mapping link to see the mapping details, related mapped fields, and links.
  8. Open the Project in Salesforce to see familiar pages from Clarizen such as Workplan and roadmap, as well as all the Clarizen fields. Click View in Clarizen to open the Project in Clarizen. You can edit in either Salesforce or Clarizen.

Note: Mappings and event triggers are explained in Triggers and Mappings.

Setting up UI Controls

UI controls are visual force pages in Salesforce that allow you to view the relevant Gantt/Roadmap in Salesforce, and access the related item in Clarizen.


To add these UI controls to the relevant objects in Salesforce , you will need to be an Admin user and follow the steps below.


  1. Access "Setup"⇒ "Develop" ⇒ "Pages" and click "New"
    You'll notice that there are already three VisualForce pages that were added as part of the Best Practices package, and are used on the new "Clarizen Project" custom object (assuming the package was installed)

    Figure 15: Creating a new VisualForce Page


Working with your Sandbox account

To configure the integration to work with your Clarizen Sandbox account please follow the steps below:

  1. Access "Setup" ⇒ "Develop" ⇒ "Custom Settings"
  2. Locate the "Clarizen Settings" with the "Namesake" CLZV6 and click "Manage"

  3. Click "Edit" for the "default" setting
  4. Change the server URL as follows
    • For Sandbox account -
    • For production account -
  5. Click "Save"
  6. Access the "Clarizen Integration Setup" tab as described above
  7. Access your Clarizen account to ensure that the system is set to allow access to Salesforce.
  8. Authenticate the relevant Sandbox (or Production) Clarizen account(s)

Re-authenticating Your Clarizen Sandbox Account After a Salesforce Refresh

When a Salesforce sandbox is refreshed, all iHub information related to the Salesforce sandbox is replaced with the Salesforce production environment details. To reconnect Clarizen sandbox with Salesforce sandbox,  you must re-authenticate Clarizen with Salesforce. 

To re-authenticate, open the Authentication tab in iHub, and re-enter the Salesforce connection details.

For more details on refreshing a sandbox account, click here.

Triggers and Mappings

This section describes the best practices triggers and mappings, as well as detailed explanations on how to create new ones. ​

What are Triggers (Events) and Mappings


An event (or trigger) is something that leads to the creation of a new object in Clarizen based on an occurrences in Salesforce and vice versa.

In this version of the integration, you can create events on any object in Clarizen or Salesforce (custom or standard), that will trigger the creation of an object in the other system.

For example, you may want to create an event that will create a Request in Clarizen each time a Salesforce Idea is created.

When creating an event that is triggered from Salesforce, you will also be able to trigger the creation of subsequent objects in Clarizen based on any related data of the original Salesforce object (more information below).


A mapping is what determines how an object in Clarizen is synced to the relevant object in Salesforce (and vice versa).

In the event example above, a Request in Clarizen is created each time an Idea is created in Salesforce.
The event determines which object to create, while the mapping determines what data is moved from Salesforce to Clarizen on the initial creation, and which data is transferred from Clarizen to Salesforce or from Salesforce to Clarizen on subsequent syncs (determined by the daily syncs).

When creating a mapping, you will also have the ability to map any related Clarizen information into new or existing objects in Salesforce (more information below). 

Best Practice Triggers and Mappings

Out-of-the-box mappings and triggers can be further customized (or completely removed/disabled) to fit your specific needs.

The out-of-the-box mappings and triggers include:


Clarizen User - SFDC User

This mapping is used to sync between a "User" in Clarizen and a "User" in SalesForce, and is specifically used when syncing between a Chatter feed in SalesForce to a discussion stream in Clarizen.
If a user doesn't exist in either system, it will create a Chatter Free user in SalesForce and an Email Only user in Clarizen. These license allocations are "hard-coded" and can't be changed in the mapping itself, although the mapping can be updated to sync the necessary fields.
The mapping is also used when syncing fields in other objects that reference the User entity (e.g. Project Manager on a Project).

Note: Existing V2 customers who would like to continue to use the "Clarizen Resource" custom object, will need to first disable this mapping and then create a new mapping between a Clarizen User and the "Clarizen Resource" custom object in SalesForce.

Account to Customer Maps an "Account" in Salesforce to a "Customer" in Clarizen and syncs the Discussion/Chatter stream between the objects.
Milestone to Milestone Maps a "Milestone" in Clarizen to a "Clarizen milestone" custom object in Salesforce
Project to Project Maps a "Clarizen Project" custom object in Salesforce to a "Project" in Clarizen. This mapping includes the linking of the "Project" in Clarizen to the relevant "Customer" in Clarizen (based on the Opportunity Account). Additionally, in subsequent syncs, the mapping will sync all project milestones (in Clarizen) as "Clarizen milestones" in Salesforce.


Create a project when Opportunity probably equals 70% The event runs each time an opportunity's probability in Salesforce is greater than or equal to 70%.
It will then create a "Clarizen Project" in Salesforce that is linked to the Opportunity, and any opportunity products will be accessed and will trigger the creation of sub-projects. 




Creating New Mappings

Mappings define exactly how objects between Salesforce and Clarizen are synced to one another (e.g. what fields are synced, what related items in Clarizen should be synced in Salesforce, etc.).

To create a new mapping:

  1. Access Mappings & Events in Clarizen or Salesforce.
  2. Click Add New > Mapping.
  3. In the Mapping Properties, enter the mapping's Name and an optional Description.
    Object mapping: In this section define what object in Clarizen will sync to what object in Salesforce.


Defines the entity of the object mapped, (e.g. Clarizen Bug will be mapped as a Salesforce Case)

Key field

Used for identification purposes, the key field will be referenced in other mappings when trying to locate a desired object (such as a project in Clarizen can be found using the External ID)

Delete policy

Determines if the item in the relevant system will be deleted or retained if the item is deleted in the other system

Create policy

Determines whether the item should be created if referenced in a separate mapping (or trigger) that doesn't yet exist, searched for using the key field, in the relevant system

Template rules

This section only opens if you choose to map a template-able object in Clarizen (such as a project or milestone).
If using the "Clarizen Project" custom object in Salesforce from the V2 integration and a template is selected within the "template" field, the template rules are overridden and the specific template indicated on the Clarizen Project during the creation is used.

·         Click Add Template.

·         Select the template to be used from the Template name menu.

·         Define the Template Criteria conditions.

·         Click Add to define additional criteria.

Note: When using multiple conditions, you can define the logical expression as either AND (default), or OR, in the Logical Expression field type OR.

Repeat the process for each template rule you wish to define.

  1. Social sync: Allows you to sync the chatter feed from an item to the Clarizen discussion feed (and vice versa)
  2. Fields Mapping: Allows you to define what fields you would like to map between the two objects. 
  3. Enable: Select to enable the specific field map.


Options include "from Clarizen" and "to Clarizen", and determines whether the data will be sent to Clarizen or will come from Clarizen


Will be filtered to match only fields fitting the data type of the Clarizen field (e.g. numeric to numeric, pick list to pick list, etc.)


Will be filtered to match only fields fitting the data type of the Salesforce field (e.g. numeric to numeric, pick list to pick list, etc.)

Event type

Options include "Create only", "sync only", and "Create and sync", and determines when the data will move in the direction specified above.

Add: click to create additional field mappings.

Note: A field map can be listed multiple times, for instance, you may want a project name to go from Salesforce to Clarizen (to Clarizen) on create only, and then on sync only to go from Clarizen to Salesforce.

  1. Create Clarizen Links: Allows you to link the Clarizen object to another object in Clarizen.
    For instance, if you want to link a newly created project to the relevant Customer in Clarizen.

    Note: This section remains hidden until Object Mapping is defined.

    1. Select the link settings from the Link [object] to list.
    2. Once the item you would like to link to is selected you will be required to select the method from the using list.

      Note: In cases where there is only one possible link this field will be hidden.

      There are two methods of identifying the item you want to create the link with:
      • Use source object field: allows you to select a field from the relevant object in Clarizen (example: opportunity.account ID)
        Selecting this option will require a mapping between the two item types and will utilize the Key field and Create policy (from Object Mapping above) to locate the object in Clarizen.

      • Identified by: Allows you to add evaluation criteria that will determine what object in Clarizen to link to.
        Complete the Field, Value type, and Value fields to determine the identification criteria.
        Click Add to create additional identification criteria.

  2. Map Related Clarizen Objects: Allows you to map objects related to the source object in Clarizen to Salesforce (example: map all milestones from the project to a Clarizen Milestone Salesforce object and link the milestones in Salesforce to the Clarizen project).
    1. Click Add Related Objects to define the object mapping.
    2. Select the object intended for mapping from the Related object list.
    3. Select the relation from the Relationship type list.
    4. Click Add to add conditions to the mapping, conditions include Source Field, Operator, and Expression.
    5. Select the map destination from the Map to Salesforce object list.
    6. Repeat the process for each mapping you wish to create.
  3. Once you have completed the mapping setup click Save.
  4. Click Enable to enable the mapping.

Creating New Events

Events define when an item will start to sync (e.g. when an opportunity in Salesforce hits 70% probability, when a bug in Clarizen is set as "reported by customer", etc.).

To create a new mapping:

  1. Access Mappings & Events in Clarizen or Salesforce. 
  2. Click Add New > Event.
  1. Enter the Name and optional Use case and Description fields. details.
  2. Triggered by: Define whether the trigger will occur in Salesforce (e.g. an opportunity is closed) or in Clarizen (e.g. a bug is set to "reported by customer").
    Once selected and after saving the Event, this specific property cannot be edited. 

  3. If you selected Salesforce
    • In the Select Triggering Object section, in the By list, enter a condition criteria that will determine when the object activates the trigger.
    • Clarizen Target Object: Select what object in Clarizen the selected Salesforce object will be mapped to, there are two options in this section:
      • Entity mapping: The selected triggering object will map directly to the selected Clarizen object (based on a mapping, either previously created or created here within).
      • Create new object and synchronize: Allows you to first create an object in Salesforce (e.g. when an opportunity hits 70% create a "Clarizen Project" in Salesforce) and then define what that object will map to in Clarizen.
        Selecting this option will also allow you to transfer field values (or constants) from the source object to the newly created Salesforce object.
    • Related objects in Salesforce: allows you to sync objects related to the selected Salesforce object to Clarizen (e.g. opportunity products are synced to milestones in Clarizen)
  4. If you selected Clarizen
    • Triggering object: Allows you to determine the Clarizen object that the trigger will run on.
      Once selected, you must enter evaluation criteria that will determine when the object activates the trigger.
    • Target object: Allows you to select what object in Salesforce the selected Clarizen object will be mapped to, if no mapping exists, you will be able to create one.
  5. Click Save when done.
  6. Click Enable to enable the event (trigger).
Have more questions? Submit a request


Powered by Zendesk