Keep Twitter API usage visible without checking manually
Add a small monthly usage check to your routine and let Notis bring potential limits to your attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Fetch tweet usage data
Fetches tweet usage statistics for a project (e.g., consumption, caps, daily breakdowns for project & client apps) to monitor api limits; data can be retrieved for 1 to 90 days.
Why this helps
Usage limits can become a surprise when no one remembers to inspect the dashboard regularly.
- See project consumption on a set cadence.
- Spot caps or unusual usage before they disrupt work.
- Avoid another recurring manual dashboard check.
Setup
Build it in a few focused steps.
- 1Connect Twitter and OpenRegister once in the Notis portal; the usage check uses Twitter data and can accompany your OpenRegister routines.
- 2Create a monthly automation or ask Notis to set up an API usage check.
- 3Write one prompt asking Notis to retrieve usage data for the chosen period and flag caps or notable changes in a concise report.
- 4Choose a monthly cron schedule and a channel for run reports.
- 5Review the first report and confirm its period and project scope.
Questions about this workflow
Does this post anything publicly?
No. The Twitter action retrieves project usage data for Notis to report.
How many days can the usage data cover?
The action supports a period from one to 90 days; ask for a period suited to your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link OpenRegister to Twitter. A trigger fires from one place; an action lands in another.
OpenRegister triggers
Twitter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a list member
Adds a user to a specified twitter list; the list must be owned by the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add post to bookmarks
Adds a specified, existing, and accessible tweet to a user's bookmarks, with success indicated by the 'bookmarked' field in the response.
Get bookmarks by user
Retrieves tweets bookmarked by the authenticated user, where the provided user id must match the authenticated user's id.
Create group DM conversation
Creates a new group direct message (dm) conversation on twitter with specified participant ids and an initial message, which can include text and media attachments.
Create compliance job
Creates a new compliance job to check the status of tweet or user ids; upload ids as a plain text file (one id per line) to the `upload url` received in the response.
Create a list
Creates a new, empty list on x (formerly twitter), for which the provided name must be unique for the authenticated user; accounts are added separately.
Create a post
Creates a tweet on twitter; `text` is required unless `card uri`, `media media ids`, `poll options`, or `quote tweet id` is provided.
Delete direct message
Permanently deletes a specific twitter direct message (dm) event using its `event id` if the authenticated user sent it; this action is irreversible and does not delete entire conversations.
Connect any two apps with Notis in the middle.
OpenRegister and Twitter, 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 Twitter.