Keep the latest Mailchimp report ready to review
Retrieve a prepared report on schedule so your weekly planning starts with the latest analysis file.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Why this helps
Reports can exist in a sandbox but remain out of sight when nobody remembers to retrieve them.
- Make prepared reports easy to access
- Support regular planning reviews
- Reduce manual file retrieval
Setup
Build it in a few focused steps.
- 1Connect Mailchimp and Codeinterpreter once in Notis.
- 2Create an automation and describe which prepared report should be retrieved.
- 3Specify the expected file location and delivery outcome in one instruction.
- 4Pick a Notis cron trigger and choose where run reports should go.
- 5Test with one existing report file and confirm it is returned.
Questions about this workflow
Where must the report file be stored?
The file should be in the Codeinterpreter /home/user folder so the Get File action can retrieve it.
Does this create the report?
No. It retrieves an existing file; use a separate workflow to generate or update it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mailchimp to Codeinterpreter. A trigger fires from one place; an action lands in another.
Mailchimp triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Campaign Trigger
Triggered when a campaign is sent or experiences an event in Mailchimp
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Profile Update Trigger
Triggered when a subscriber's profile is updated in Mailchimp
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
Subscribe Trigger
Triggered when a subscriber subscribes to Mailchimp
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Unsubscribe Trigger
Triggered when a subscriber unsubscribes from Mailchimp
Connect any two apps with Notis in the middle.
Mailchimp and Codeinterpreter, 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 Codeinterpreter.