Grid Squid Glossary
Records
A Record in a CRM represents an individual entry under a specific Object, containing the data for a particular customer, lead, or entity. For example, an Accounts Object may have multiple Records, each representing a unique account with fields such as name, email, revenue and more. When Grid Squid interacts with a connected CRM platform, it retrieves the requested Record(s) based on the integration query. The returned data can be: RAW Records: Unaltered data as it exists in the CRM. (if mapping is not defined for that Object) TRANSFORMED Records: Data that has been processed and formatted according to the rules defined in your Mapping configuration. This flexibility allows you to work seamlessly with CRM data in its original form or as a standardized structure that aligns with your specific business requirements.
Fields
Fields represent the specific pieces of information or attributes associated with a CRM Object. These fields define the structure and data points for an object, allowing it to store relevant information. For example, an Accounts Object may include fields such first_name, last_name, email, address, status, revenue etc. The type, structure, and number of fields for a CRM Object depend on the specific CRM platform being connected to. Some CRMs may have fixed fields, while others support custom fields that can be tailored to specific business needs. Grid Squid is designed to seamlessly adapt to the CRM's field structure during integration. This ensures compatibility with various CRMs, enabling efficient interaction and data management across platforms without requiring manual adjustments.
Objects
Objects are the top-level entities in any CRM system, representing key data categories or modules used to organize and manage information. Common examples of CRM Objects include Accounts, Contacts, Leads, Opportunities, and more. The type of Objects and their naming conventions can vary depending on the specific CRM platform. For instance, some CRMs may refer to "Accounts" as "Organizations" or have additional unique Objects tailored to their system. To maintain consistency and simplify integration, Grid Squid standardizes these entities by referencing them uniformly as CRM Objects, regardless of the specific CRM's terminology or structure.
Events
Events in Grid Squid are used to notify users of changes occurring on the CRM side. Users can configure events to monitor specific CRM objects for updates. Grid Squid periodically checks for changes at user-defined intervals, known as the polling time. When a change is detected, a notification is sent to the user via a predefined notification URL.
Bulks
Bulk export in Grid Squid enables the retrieval of large volumes of data from a CRM for a specific object. This functionality is particularly useful for initial data loading or syncing large volumes of CRM data into the system efficiently. Before creating a bulk export request, a mapping for that object has to be created. Bulk export uses the mapping configuration to transform the data from the CRM. The data retrieved through a bulk import respects the access level and permissions of the individual user in the CRM.
Users
A User is an individual associated with a company in Grid Squid. Each user must authenticate with their individual CRM credentials (e.g., username and password or access tokens) to access CRM data, objects, and activities. Users share access to mappings and bulk imports created within their company.
Mapping
A Mapping in Grid Squid is a customizable workflow designed to extract, transform, and prepare CRM data for integration with other applications. Users can specify the CRM object (e.g., leads, opportunities) and define the fields required by the target system. Advanced transformations, such as validations, filtering and data quality checks, can be implemented using custom JavaScript. Mappings are created within a company and shared among all its users. The data retrieved through a mapping respects the access level and permissions of the individual user in the CRM.
Company
Company in Grid Squid represents a group of users pointing to a specific CRM instance. For example, a company named SF1 is pointing to a Salesforce CRM instance and contains 3 users who share access to all company resources.
