Core Elements
/
Overview
Last updated

Core Elements Overview

The core elements of the Fluid Mobile and Desktop apps are features that let companies and third-party developers build innovative business approaches without requiring users to juggle multiple common business applications.

Think of these Core Elements like the default apps on an iPhone—they're reliable tools that all users need at a basic level to share brand content and manage their business effectively.

All of these items are available in the User API Reference to read and write necessary data.

Core Elements

Activities

Push notifications and activity feed that link to resources inside of the mobile and desktop applications. Activities keep users informed of important events and updates in real-time.

Activities can be associated to a Contact.

Catch Ups

Daily swipable card reminders of what reps should pay attention to. These action cards give a summary and an action to reps, helping them stay focused on their most important priorities each day.

Catch Ups can be associated to a Contact.

Tasks

Tasks are the simple to-dos or reminders feature to keep reps organized. You can push tasks to a rep via the API to remind them of important to-dos in their organization.

Tasks can be associated to a Contact.

Notes

A simple notepad for reps to write down important information in their CRM. Notes help reps capture details about conversations, preferences, and other relevant information.

Notes can be associated to a Contact.

Events

A standard calendar view for the User. Companies and Droplets may add events to the User's calendar to remind them of important dates such as meetings, trainings, and promotional deadlines.

Contacts

The core CRM component of Fluid's mobile application. Sync contacts from phone and/or back office. Contacts are automatically added for all new Customers in the Rep's organization, making it easy to manage customer relationships.

Note: Resources that can be associated to a Contact will show up on the Contact card in the associated tab, as well as in the main list view of that feature.

Accessing Core Element Data

Fluid's unique architecture provides both Company and User APIs to access the same resources based on the ownership of the data.

API URL Structure

To access these elements, you'll use a scoped API endpoint:

GET /api/company/crm/v202506/events/:id
SegmentDescription
company or userIndicates what type of authentication is being used
crmThe scope required to access the given data. See the API Overview guide for a list of available scopes
v202506The version of the API
eventsThe resource being accessed
:idThe resource identifier (optional, depending on the action)

Use the appropriate HTTP verb and identifier to complete the actions you desire.

Authentication

Since data can be owned by the Company, the User, or both, the list and access will vary based on your approach.

User Access: A User must authenticate via Fluid Auth, and the requester would follow the token exchange to access the User endpoints.

Company Access: A Company token can be generated in the admin portal under Developer Settings.

Data Ownership & Access

Contact Structure

{
  "first_name": "Jane",
  "last_name": "Smith",
  "email": "jane.smith@example.com",
  "rep_id": "12345",
  "company_id": "67890",
  ...
}

Example: Company-Accessible Contact

When a Contact has both company_id and rep_id present, it is accessible via the Company API:

{
  "first_name": "Jane",
  "last_name": "Smith",
  "email": "jane.smith@example.com",
  "rep_id": "usr_12345",
  "company_id": "cmp_67890",
  ...
}

Since the company_id is present, this Contact is accessible via the Company API to view and modify. Contacts generated from the Company website or marketing campaigns would be available to the Company to view and modify later.

Example: User-Only Contact

When a Contact only has rep_id present, it is only accessible via the User API:

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john.doe@example.com",
  "rep_id": "usr_12345",
  "company_id": null,
  ...
}

This Contact is available via the User-scoped API, but would not be accessible from the Company scope. A User would have to give authorization to an application to access this data. These Contacts are typically inserted from a phone contact sync or imported via Connect. A User can also manually add Contacts to their CRM.

Access Structure for All Core Elements

This same access structure exists for all Core Elements.

  • Company APIs give the ability to add Tasks, Events, Activities, Catch Ups, Notes, and Contacts to a User in their organization
  • User APIs provide access only to that User's own data—User auth does not give permission to add or retrieve data from other Users or the Company

Next Steps

Previous page
Next page