Skip to main content

​
🔁 Rotation Rules

Rotation rules let you define a single key with multiple values that Nota rotates on a schedule.
Use them for expiring tokens, limited-use test accounts, promo codes, or any data that should change over time.

​
Key Concepts

SettingDescriptionExample
KeyThe name you reference in workflows.API_KEY, QA_USER_EMAIL
ValuesA list of values Nota cycles through.["sk_test_a", "sk_test_b", "sk_test_c"]
Start DateWhen rotation begins; nothing rotates before this date.2025-06-01
IntervalHow often Nota advances to the next value.Hourly, Daily, Weekly, Monthly, Custom

​
Supported Intervals

IntervalWhen it advances
HourlyAt the top of each hour
DailyEvery calendar day
WeeklyEvery 7 days
MonthlySame day each month
CustomSpecify the number of days between rotations
📅 Start Date Matters: Nota uses the start date as the anchor point when calculating which value should be active at runtime.

​
Create or Edit a Rule

  1. Go to Settings → Rotation Rules.
  2. Click ➕ Add Rule or select an existing rule to adjust.
  3. Enter the Key, list of Values, Start Date, and Interval.
  4. Save—Nota immediately begins serving the correct value based on the schedule.

​
Bulk Upload via JSON

Upload multiple rules at once using a JSON file. Each rule follows this structure: 
[
  {
    "key": "API_KEY",
    "values": ["sk_test_key_1", "sk_test_key_2", "sk_test_key_3"]
  },
  {
    "key": "EMAIL_ACCOUNT",
    "values": ["[email protected]", "[email protected]"]
  }
]
Review mappings before saving to avoid accidentally overwriting existing schedules.

​
Real-World Example

Rotation rules configuration This setup rotates an email API key every month starting June 1—perfect for credentials that expire or get rate-limited.

​
Best Practices

  • Pair with Environment Variables: Store the rotation key once, then consume it via environment variables in workflows.
  • Test ahead of time: Use a closer start date in staging to validate behavior before mirroring in production.
  • Document ownership: Note who maintains each rule so rotations stay coordinated with downstream systems.