Articles on: PipeLaunch Salesforce App

Salesforce Custom Objects Included on the Package

When you install the Pipelaunch managed package, several custom objects and settings are added to your Salesforce environment. These objects are essential for storing data related to prospecting signals, job openings, and configuration settings.

This guide provides a breakdown of these objects so System Administrators can understand their purpose and security requirements.


Core Application Objects

These objects are central to the main functionality of the application, used for tracking intelligence and logs.


Object Name

API Name

Description

PipeLaunch Signal Log

PipelaunchSignal__c

Stores PipeLaunch Signals for a record (e.g., fompany change, name mismatch).

Job Opening

JobOpening__c

Sample object to store a job opening, with description, job title, job posting date, etc.

PipeLaunch Log

PipelaunchLog__c

Used for system diagnostics and error logging.

Custom Activity

activity__c

An internal custom object used to handle specific activity logic distinct from standard Salesforce Tasks/Events.


Sales Engagement Add-on Objects


The following objects are specifically required for the Sales Engagement feature.


Objection Handling

  • Common Objection (Common_Objection__c): The master record for a specific objection type.
  • Common Objection Label (Common_Objection_Label__c): Stores display labels for objections to ensure users see the correct terminology.
  • Common Objection Link (Common_Objection_Link__c): A junction object linking objections to specific scenarios or scripts.


Scripts & Pitches

  • Script Scenario (ScriptAndPitch_Scenario__c): Defines the context of a call (e.g., "Cold Call," "Follow-up").
  • Script (ScriptAndPitch_Script__c): The actual content/text of the script.
  • Script Label (ScriptAndPitch_Script_Label__c): Display names and categorization for scripts.
  • Script Links (ScriptAndPitch_Script_Links__c): Connects scripts to specific scenarios or objection flows.


Planning & Target Lists

  • Planning (Planning__c): The header object for a specific sales plan or campaign strategy.
  • Planning Contacts (Planning_Contacts__c): Associates specific Contact records with a Plan.
  • Target List (target_list__c): A container for a static or dynamic list of targets.
  • Target List Account (Target_List_Account__c): Junction object linking Accounts to a Target List.
  • Target List Contact (Target_List_Contact__c): Junction object linking Contacts to a Target List.


Configuration & Custom Settings

These objects are primarily for System Administrator use. They control how the application behaves, how fields map, and where data is sourced.

Object/Setting Name

API Name

Type

Description

Core Setting

CoreSetting__mdt

Custom Metadata

Defines fundamental app behaviors and API connection

News Sources

news_sources__mdt

Custom Metadata

Configures the external sources used to fetch news

Planning Filter

PipeLaunch_Planning_Filter__mdt

Custom Metadata

Controls logic for filtering records within the Planning module

Field Mapping

CustomFieldMapping__c

Custom Setting

Manages the mapping logic

Pipelaunch Setting

PipelaunchSetting__c

Custom Setting

General configuration settings for the package

General Settings

generalsettings__c

Custom Setting

Stores global preferences for the application usage

Logging Config

Pipelaunch_Logging__c

Custom Setting

Controls the verbosity and activation of system logs


Extensions to Standard Objects

The package also includes custom fields on standard Salesforce objects to facilitate data enrichment.

  • Account: Fields added to store company-level intelligence.
  • Contact: Includes fields like social network URL for social selling integration.
  • Lead: Includes fields for Contact Insights and error handling.
  • Activity: Custom fields added to standard Tasks/Events to track activity outcomes generated by the package.


Updated on: 17/02/2026