The time has finally come for PushMetrics 1.0! We're proud to present the final changes that we packed into this release!
Notebooks are now executed in a script-like manner. Meaning they can do (almost) anything you could do in a Python script, or an Airflow DAG.
For that, we have added these blocks (so far):
- Slack block
- Email block
- API block
- JINJA for execution logic (IF and FOR-LOOPS)
The idea is that you can re-create any repetitive task in a well-documented, shareable PushMetrics Notebook. Whenever you have to do that task again, you simply
execute the Notebook or Page. Or you simply schedule it to execute by itself.
You win, because you safe time and work, especially when things are repetitive.
Your Team wins, because you can now build on top of each others work, get insight into what others are building. All in the complete context of a workflow.
I am sure that some of the following tasks will seem familiar:
Well, you can do all of that now. Once. And then you schedule or execute ad-hoc.
Let's have a quick look at these new block-types:
Send messages to slack on demand or schedule. Any JINJA references, as with all blocks, will be resolved automatically.
A well designed KPI Slack message is probably one of the easiest ways to keep yourself and the Team informed without having to dig through databases and dashboards.
Wrap a block like this into an
IF clause to create an alert anytime.
The example below shows an Email block wrapped into a
FOR loop. This would send a message for each
row returned by the SQL block named
Being able to colaborate on API Calls and workflows that build on APIs is, for me, the most exciting new feature.
Reference data from a SQL block in your API call to enrich data in services like Intercom, Salesforce, or almost anywhere else.
Once a API block is designed you and your Team can duplicate and reuse it anywhere else.
Last but not least: For loops and IF statement is how you can now orchestrate execution logic in your Notebooks. Feel free to combine these as much as you like.