Keep customer requests from getting lost in chat
Notis checks recent 2chat conversations for explicit product requests and records the supported details in Databox.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Push Data to Dataset (V1)
Tool to push data points to a Databox dataset using the v1 API. Use when you need to ingest data records into a specific dataset by providing the dataset ID and an array of records matching the dataset schema.
Why this helps
Product ideas shared in private chats can disappear before they reach a planning conversation.
- Gather explicit requests from recent customer conversations.
- Keep product feedback easier to review over time.
- Reduce manual transfer of feedback from chat.
Setup
Build it in a few focused steps.
- 1Connect 2chat and Databox once in the Notis portal.
- 2Create an automation and tell Notis to identify explicit feature requests in recent conversations and push supported details into your Databox dataset.
- 3Pick a recurring schedule as the trigger.
- 4Choose where run reports should go.
- 5Test with one conversation containing a request and verify the resulting record.
Questions about this workflow
Will this invent feature requests from general complaints?
Ask Notis to capture only requests explicitly stated in the chat. General problems should remain labeled as problems if your dataset supports that distinction.
Does this prioritize the roadmap?
No. It records request signals; prioritization requires additional context such as product strategy or customer impact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Databox. A trigger fires from one place; an action lands in another.
2chat triggers
Databox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Dataset
Tool to create a new dataset in Databox data source. Use when you need to initialize a dataset with a title, data source ID, and primary keys for unique record identification.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Data Source
Tool to create a new data source in Databox. Use when you need to create a logical container for datasets within a Databox account. Requires accountId, title, and timezone parameters.
Delete Dataset
Tool to delete a dataset by ID in Databox. Use when you need to permanently remove a dataset. This operation is irreversible.
Delete Data Source
Tool to delete a data source by ID in Databox. Use when you need to permanently remove a data source. This operation is irreversible and will delete all associated datasets.
Get Dataset Ingestion Status
Tool to check the status of a specific data ingestion for a dataset. Use when you need to verify whether a data ingestion was successful by providing the dataset ID and ingestion ID returned from the initial POST request.
List Accounts
Tool to retrieve all Databox accounts accessible to the authenticated user. Use to identify account IDs required for subsequent API operations like data source creation.
Push Data to Dataset (V1)
Tool to push data points to a Databox dataset using the v1 API. Use when you need to ingest data records into a specific dataset by providing the dataset ID and an array of records matching the dataset schema.
Connect any two apps with Notis in the middle.
2chat and Databox, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Databox.