When creating data sources in Plecto, think of them as tables in an SQL database. This is not exactly how we store them, but conceptually it's very similar. Here are some good-to-knows:
As Plecto currently does not support joins, please make sure to include any necessary information for filtering purposes inside each "row." In addition, make sure that all data is encoded in utf-8.
Plecto has certain API limits – you can send up to 100 registrations per request and total max of 3600 requests per hour.
Here's a list of field names, types and descriptions that make up Plecto's API data model:
UUID of a Plecto data source which you must create first via the GUI or dedicated API methods.
ISO 8601 with timestamp
Primary date of this data registration. For example, for a sales opportunity, you could use the expected close date. You can add more date fields, but this will be the default.
Name of the system where the member_api_id and member_name originate. For example, Salesforce, Podio, datawarehouse, activedirectory.
Employee ID in the member API provider's database.
Full name of the employee.
Unique ID of a registration.
You can add more fields from the GUI or via data source API methods.