Flows and automation
Flows that filter your data and send at the right time
A DeepMiner flow starts from an index and groups strategies. Each strategy has filters on the data fields, a provider linked to the index and a recurrence: manual, once, daily, every N hours, on weekdays or by cron expression. Before saving, you see how many records will be reached. Each send creates a run with real-time progress, sent messages, failures and the amount debited.
What you do
Strategies with filters, provider and recurrence. Each send becomes a tracked run.
-
Filters with an expected count
Build the cut with operators such as is one of, contains, between, greater than and last 30 days. The Expected records field shows how many records the strategy will reach.
-
Recurrence your way
Manual, once at a date and time, daily at HH:mm, every N hours, on weekdays or advanced cron, always with a time zone.
-
No resending to people who already received
Check the option and the strategy skips records that already have a send logged on that channel. A per-run limit controls the volume of each send.
-
Tracked runs
Each send, manual or scheduled, appears under Runs with status, progress, total, sent, failures, amount debited and origin. A run in progress can be canceled.
How a flow works
Open the index in Flows and create a strategy. Give it a name, build the filters, choose the provider and set the recurrence. Only active providers with a complete mapping are listed, so a strategy cannot be saved with a half-finished link.
Strategies appear as cards under the index. Each card shows the filters, the next run, the last run and how many records were sent. The order of the cards can be adjusted.
Filters on your data
Filters use the fields of the index schema. Text accepts is one of, is not one of, contains and exists. Number accepts equality, greater, less and between. Date accepts the last 7, 30 or 90 days or a custom range, and boolean accepts true or false.
Sensitive fields require you to type the value and do not show the list of values in the data. Record metadata, such as import status and import date, can also be used in the filter. That makes it possible to send only to people imported in the last week.
Runs
Each send creates a run. The runs screen lists the status, the strategy, the progress, the total records, the sent messages, the failures, the amount debited, the date and the origin, manual or scheduled. Progress updates in real time, and the run detail leads to the index records, where each provider’s result appears.
Frequently asked questions
Flows and automation
Do I need to code to schedule a send?
No. Common recurrences are picked in a form. Cron is available for anyone who needs a more specific schedule.
How do I know how many people will receive it before sending?
The strategy shows the expected records based on the filters, before you save.
Can I pause a strategy?
Yes. Each strategy can be paused, resumed, run right away, edited or deleted, and the card shows the next and last run.
What happens if the balance runs out?
The run stops when the balance does not cover the next batch and gets the Insufficient balance status. What was already sent stays counted in the run, and the rest does not go out.
Are flows only for messages?
No. A strategy uses any active provider linked to the index, including data enrichment providers.
See DeepMiner working on your data.
Book a demo and watch a dataset get indexed, enriched and queried.