Review Onepage token metadata every month
A monthly token details lookup gives access metadata a predictable review point, instead of leaving it to memory.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Token details request
Retrieves detailed information about a specific token in the onepage system. this endpoint should be used when you need to obtain comprehensive data about a token, such as its associated permissions, expiration date, or other metadata. it's particularly useful for token management tasks, such as verifying token validity or checking token attributes. the endpoint accepts a single token and returns its corresponding details. it should not be used for token creation, deletion, or modification operations. note that the specific details returned may vary based on the onepage implementation and the token's type or purpose.
Why this helps
Permissions and token metadata can go unreviewed when checks have no place on the calendar.
- Give token metadata a recurring review point.
- Make returned permission details easier to revisit regularly.
- Reduce the mental load of remembering an occasional check.
Setup
Build it in a few focused steps.
- 1Connect Metaads and Onepage to Notis once in the portal and securely configure the token for lookup.
- 2Create a plain-language instruction for Notis to retrieve and summarize the token details returned by Onepage.
- 3Choose a monthly cron trigger and select a channel for run reports.
- 4Test the lookup and confirm the summary includes the metadata your review needs.
Questions about this workflow
Does the workflow change permissions?
No. It retrieves token details for review and does not change permissions.
What if the endpoint does not return expiration information?
The workflow can only report metadata that the Onepage endpoint returns.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Metaads to Onepage. A trigger fires from one place; an action lands in another.
Metaads triggers
Onepage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search input post request
The searchinput endpoint allows users to perform a search query within the onepage platform. it accepts a required search string and optional parameters for language and output format customization. this endpoint is designed for retrieving relevant information based on user-specified search terms, with the ability to filter results by language and choose between structured (json) or plain text output. use this endpoint when you need to search for specific content or information within the onepage ecosystem. it's particularly useful for integrating search functionality into applications or workflows that interact with onepage data. note that this endpoint focuses solely on search functionality and does not provide additional features like content creation or modification.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Token details request
Retrieves detailed information about a specific token in the onepage system. this endpoint should be used when you need to obtain comprehensive data about a token, such as its associated permissions, expiration date, or other metadata. it's particularly useful for token management tasks, such as verifying token validity or checking token attributes. the endpoint accepts a single token and returns its corresponding details. it should not be used for token creation, deletion, or modification operations. note that the specific details returned may vary based on the onepage implementation and the token's type or purpose.
Connect any two apps with Notis in the middle.
Metaads and Onepage, 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 Onepage.