Overview
This FAQ is to address questions regarding custom objects in Outreach.
Applies To
- Outreach Admins
- Custom Objects
Frequently Asked Questions
What is a custom object?
A custom object is a user-defined object with unique fields and permissions. Custom objects can represent almost anything - campaigns, products, subscriptions, competitors, or demos.
Customers can extend Outreach with custom objects to store information specific to their business needs to support their sales actions and workflows.
Who can use the custom objects feature?
Custom objects can be defined by administrators and used by Outreach end-users.
Are there any limitations to custom objects?
Customers can create and use up to 5 free custom objects per org. In addition, the following limits apply to each custom object:
- Max number of all fields: 100
- Max number of lookup fields to a specific object
- Prospects: 3
- Accounts: 3
- Opportunities: 3
- Users: 10
- Custom objects: 10
Who can create custom objects?
Currently, only org admins can create and administer custom objects. Once created, custom objects can be used by all users with permission to do so. Permissions are defined by org admins.
What types of fields can be added to custom objects?
Admins can add various types of fields such as text, number, date, dropdown lists, and more, providing flexibility to capture the required data accurately.
What field validations are supported?
Currently, the only field validation supported is the required field validation. This ensures that certain fields must be filled out before a record can be saved, helping to maintain data integrity and completeness.
Are formula fields supported?
No, formula fields are not yet supported within custom objects. This feature is not currently available but may be considered for future updates.
Are roll-up fields supported?
No, roll-up fields are not supported within custom objects. This feature is not currently available.
Can custom objects have relationships with other objects?
Yes, custom objects can have relationships with other objects.
Admins can currently create relationships from custom objects to other custom objects, and to the following standard objects: Prospects, Accounts, Opportunities, and Users.
Can a custom object have a relationship with itself?
Yes, custom objects can be associated with themselves. This way, users can create a hierarchy within the same object.
What happens when a custom object is deleted?
When a custom object is deleted:
- All associated records are permanently deleted.
- Lookup fields referencing this custom object will be deleted.
- Any triggers involving the custom object will be deactivated.
This action is irreversible and cannot be undone.
Is it possible to surface custom objects in the main navbar?
Yes, administrators can choose to surface custom objects in the main navigation bar, providing users with quick access through a dedicated section within the interface. This option can be configured in the ‘General’ tab of each specific custom object.
What systems can custom objects sync with?
Custom objects can be synced with external systems and databases such as CRMs via a native CRM sync in Outreach or the Public API, ensuring seamless data integration and up-to-date information across platforms.
Is the sync with Dynamics supported?
No, currently only the sync with Salesforce is supported. Dynamics is currently considered for future releases.
Can user permissions be configured for custom objects?
Yes, administrators can configure user permissions for custom objects, allowing control over who can access and modify the data to maintain security and integrity. Permissions are assigned based on user profiles. Currently, owner-based permissions are not supported.
Is field-level security supported on custom objects?
Currently, user permissions cannot be set for individual fields on custom objects. Permissions can only be managed at the custom object level, controlling access and editing rights for the entire object rather than specific fields within it.
Is it possible to build triggers based on custom objects?
Yes, admins and users with permissions can create triggers using custom objects. It is possible to select a custom object as both source and target object as well as set conditions on custom objects.
Can custom objects be used for reporting?
Currently, custom objects cannot be used for reporting directly. However, the data within custom objects can still contribute to overall insights and can be utilized in other ways to indirectly inform reporting processes.
Can custom objects be used for forecasting?
Currently, custom objects cannot be used for forecasting. However, data from custom objects can still contribute valuable insights that indirectly inform overall forecasting processes.
Is there a public API available?
Yes, a public API is available for custom object records, enabling the creation, retrieval, update, and deletion of records within custom objects. This API will be documented in the REST API section of the development portal once the feature is released. For more information, visit the Outreach Development Portal.
Can custom objects be used to track activities?
Activity records such as emails, calls, and tasks cannot be currently associated with custom objects.