Configuring Wootric as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Wootric option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
You’ll need your Wootric account credentials for this connection.- Username: The username to authenticate against the API service.
- Password: The password to authenticate against the API service.
- Start date: Records created or updated after the start date will be extracted from the source.
2. Select streams
Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. Wootric provides access to end user data and survey responses.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Below you’ll find all available data streams from Wootric and their corresponding fields:End Users
End Users
Stream containing end user data and their survey preferences.
| Field | Type | Description |
|---|---|---|
id | String | Unique system identifier for the user |
email | String | User’s email address |
external_id | String | External identifier for the user |
phone_number | String | User’s phone number |
created_at | String | When the user was created |
updated_at | String | When the user was last updated |
last_surveyed | String | When the user was last surveyed |
external_created_at | String | External timestamp when the user was created |
last_seen_at | String | When the user was last seen |
properties.name | String | User’s name |
properties.role | String | User’s role |
properties.domain | String | User’s domain |
properties.language | String | User’s language preference |
last_response.id | String | ID of the last response |
last_response.score | Integer | Score of the last response |
last_response.text | String | Text of the last response |
last_response.survey.channel | String | Survey channel used |
settings.email_nps | Boolean | Whether email NPS surveys are enabled |
settings.mobile_nps | Boolean | Whether mobile NPS surveys are enabled |
settings.web_nps | Boolean | Whether web NPS surveys are enabled |
settings.force_mobile_survey | Boolean | Whether to force mobile surveys |
settings.force_web_survey | Boolean | Whether to force web surveys |
settings.surveys_disabled_by_end_user | Boolean | Whether surveys are disabled by the user |
Responses
Responses
Stream containing survey responses and feedback data.
| Field | Type | Description |
|---|---|---|
id | String | Unique system identifier for the response |
end_user_id | String | ID of the user who provided the response |
survey_id | String | ID of the survey this response belongs to |
score | Integer | Numeric score provided in the response |
text | String | Text feedback provided with the response |
completed | Boolean | Whether the response was completed |
excluded_from_calculations | Boolean | Whether this response is excluded from calculations |
ip_address | String | IP address where the response originated |
origin_url | String | URL where the response originated |
created_at | String | When the response was created |
updated_at | String | When the response was last updated |
tags | String | Tags associated with the response |
notes | String | Notes associated with the response |
end_user.email | String | Email address of the responding user |
end_user.external_id | String | External identifier of the responding user |
end_user.external_created_at | String | External creation timestamp of the user |
end_user.created_at | String | Creation timestamp of the user |
end_user.properties | String | Additional user properties (stored as JSON string) |
Data Model
The following diagram illustrates the relationships between the core data streams in Wootric. The arrows indicate the join keys that link the different entities, providing a clear overview of the data structure.Skills for agents
Download Wootric skills file
Wootric connector documentation as plain markdown, for use in AI agent contexts.