Use “Peer: request an appointment” in Recued. It carries out the named workflow using the connections and settings you choose.
Peer: request an appointment
Use “Peer: request an appointment” in Recued. It carries out the named workflow using the connections and settings you choose.
Complete workflow
Peer Exchange (outbound)
8 pinned recipes
Use Peer Exchange (outbound) in Recued. It includes 7 built-in actions and 4 ready-to-run workflows, and carries the operations a peer conversation travels over — including putting a question to a peer's owner, routing one to their authorizing recipe instead, and carrying their answer home.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Ask a peer for an appointment” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Peer: appointment answered” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “Ask a peer to update a federated project” in Recued. It carries out the named workflow using the connections and settings you choose. Changes remain behind Recued's approval controls.
Use “Land a peer's answer to a federated project update” in Recued. It carries out the named workflow using the connections and settings you choose.
Use “What happened to my exchange” in Recued. It carries out the named workflow using the connections and settings you choose.
Show all 8 recipes
Use “Ask a peer's owner a question” in Recued. Puts one question to a person on another Recued server and waits for their answer — this run pauses, they see the question wherever they read notifications, and it continues when they reply. Nothing of yours runs or is readable on their machine.
Use “Authorize a peer's held continuation” in Recued. Another server has paused a run and asked you to approve it. This reads the evidence they sent, judges it against the policy you wrote, and sends your decision back. Anything short of a clear approval refuses; if it cannot judge at all it stays silent, and their own deadline decides.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (15 steps)
require_contract
template
Generate text from a template
fail: context.caller.contract_id is_null
exchange_ref
trim
Trim whitespace from setting exchange ref
exchange_ref_required
template
Generate text from a template
fail: step.exchange_ref is_empty
start_ms
to_number
Convert setting proposed start to a number
end_ms
to_number
Convert setting proposed end to a number
window_ordered
compare
Check if end ms is greater than start ms
window_guard
template
Generate text from a template
fail: step.window_ordered equal false
lookback_ms
to_number
Convert setting straddle lookback ms to a number
scan_from
math
Calculate: {{step.start_ms}} - {{step.lookback_ms}}
events_raw
core.data.calendar.list
List data calendar
events
default
Apply default
live_events
filter
Filter by condition
timed_events
filter
Filter by condition
conflicts
filter
Filter by condition
conflict_count
count
Count items in conflicts
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
errors
setting
=
[object Object]
outcome
setting
=
[object Object]
subject
setting
=
[object Object]
action ref
setting
=
[object Object]
scan limit
setting
=
200
callback op
setting
=
recued-core/peer-appointment-reply
exchange ref
setting
=
[object Object]
proposed end
setting
=
[object Object]
calendar slug
setting
=
work
proposed start
setting
=
[object Object]
peer connection
setting
=
[object Object]
straddle lookback ms
setting
=
21600000
Uses (1 operation)
Calendar
List data calendar
core.data.calendar.list
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Read
Calendar
core.data.calendar.list
read-only