Review Campayn email reports on a steady schedule
Bring delivery report links and metadata into a regular review so campaign follow-up is easier to keep moving.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Reports
Tool to retrieve report urls and metadata for sent and scheduled emails. use when you need to fetch email delivery data, optionally filtered by a date range (unix timestamp in seconds, utc). note: scheduled emails will have report url set to null.
Why this helps
Campaign results can be scattered across report pages, making it easy to postpone the review.
- Collect available report links and metadata in one scheduled run.
- Make campaign review a predictable routine.
- Use a date range when the automation prompt supplies one.
Setup
Build it in a few focused steps.
- 1Connect Campayn once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, say to retrieve Campayn reports and summarize available metadata and report URLs, using a stated date range if desired.
- 4Pick a recurring schedule as the trigger.
- 5Choose where run reports go, then test with one real example.
Questions about this workflow
Will scheduled emails have a report URL?
Campayn's Get Reports action may return a null report URL for scheduled emails.
Can I limit the report window?
Yes. The action supports an optional date range in Unix timestamp seconds using UTC; provide the desired range in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Campayn. A trigger fires from one place; an action lands in another.
Jira triggers
Campayn actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to create a new contact in a specific list. use when you need to add a contact after gathering details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Contact
Tool to delete a specific contact. use when you need to remove a contact permanently after confirming it should be deleted. example: "delete contact 123".
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete List
Tool to delete a specific contact list. use when cleaning up unused lists after confirming they are no longer needed. example: "delete list 123".
New Project
Triggered when a new project is added in Jira
Delete webform
Tool to delete a specific webform. use when removing outdated or unnecessary webforms after confirming they are no longer needed. example: "delete webform 123".
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Get Contact
Tool to retrieve a specific contact by id. use when you need to fetch full contact details after confirming the contact id.
Get Contacts
Tool to retrieve all contacts in a specified list. use when you need to fetch list contacts after confirming list id.
Get List
Tool to retrieve a specific contact list by id. use when you need to fetch list details like name, tags, and contact count after knowing the list id.
Get Lists
Tool to retrieve all contact lists. use when you need to fetch available lists before performing list-specific actions. example prompt: "list all my contact lists".
Connect any two apps with Notis in the middle.
Jira and Campayn, 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 Campayn.