Skip to content
Recued
Menu
← Back to recipes

Allocate Maxio component

by recued-core v1

Approval-gated Maxio component allocation workflow. It reads the subscription component, previews the allocation object when provided as a single-allocation list, creates exactly one allocation through recued-core.maxio, and returns allocation history. It does not record metered usage, create subscriptions, create invoices, alter coupons, handle payment profiles, refund, void, delete, or call arbitrary Maxio endpoints.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)
component ?
preview ?
created_allocation ?
allocations_raw ?
allocations default
Apply default
allocation_rows slice
Take a subset of
allocation_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

maxio setting =
row limit setting = 12
allocation setting = [object Object]
component id setting = 0
subscription id setting = 0

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Maxio connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

maxio maxioallocationcomponentssubscriptionapprovalpack:maxio

Details

8 steps 5 configurable settings recipe_id: allocate-maxio-component