Put subscriber context beside the signup event
Keep the relevant research file close to the new signup so analysis starts with the right context.
Trigger
Subscribe Trigger
Triggered when a subscriber subscribes to Mailchimp
Action
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Why this helps
Useful audience research often lives in a separate file that gets overlooked during onboarding.
- Keep analysis inputs together
- Reduce file hunting
- Improve consistency of subscriber reviews
Setup
Build it in a few focused steps.
- 1Connect Mailchimp and Codeinterpreter once in Notis.
- 2Create an automation and describe which supplied file should be uploaded.
- 3State the desired filename and how the file should support analysis.
- 4Pick the Mailchimp Subscribe Trigger and choose the report destination.
- 5Test with one real subscription and verify the file is available in the sandbox.
Questions about this workflow
Where does the file come from?
The file must be supplied or made available to the automation; Mailchimp does not provide arbitrary external files.
Can the upload be followed by analysis?
Yes. Include the requested follow-up analysis in the same plain-language instruction when the inputs are available.
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.