iCalendar Respond

Description

The iCalendar Respond node builds the standard RFC 5545 answer to an invitation:

• accept / decline / tentative → a METHOD:REPLY with the corresponding PARTSTAT.
• counter → a METHOD:COUNTER proposing a new date/time (and optionally a new location).

It is designed to consume the output of iCalendar Extract: when connected after it, the UID, organizer, summary and sequence are taken from the event automatically — you only choose the action and say who is answering. Any of those fields can be overridden in the configuration.

The output includes the .ics text plus everything needed to send it with Send Mail: suggested subject, the organizer’s address in to, a filename and the correct text/calendar; method=… MIME type.

Configuration

Parameters

Parameter	Type	Required	Description
action	text	Yes	accept, decline, tentative or counter (Spanish aliases work too: aceptar, rechazar, tentativo, modificar). Supports variables, e.g. {{decision}}
attendeeEmail	text	Yes	Email of the person answering (must be an invited attendee)
attendeeName	text	No	Display name for the attendee
comment	text	No	Message for the organizer (sent as COMMENT)
newStart	text	counter only	New start, ISO format: 2026-09-02T10:00:00Z (a date-only value creates an all-day proposal)
newEnd	text	No	New end, ISO format
newLocation	text	No	Proposed location (counter only)
uid / organizerEmail / organizerName / summary / sequence	text	No	Overrides — filled automatically from the incoming event when connected after iCalendar Extract

Output

{
  "ics": "BEGIN:VCALENDAR\r\nPRODID:-//Floogos//icalRespond 1.0//ES\r\n…",
  "method": "REPLY",
  "partstat": "ACCEPTED",
  "uid": "7f3k2m9q@google.com",
  "filename": "reply.ics",
  "mimeType": "text/calendar; method=REPLY; charset=UTF-8",
  "subject": "Aceptada: DWH integration review, sprint 12",
  "to": "laura@example.com",
  "event": { "…": "the original event, passed through" }
}

For action: counter, method is COUNTER, partstat is NEEDS-ACTION and filename is counter.ics.

Usage Examples

Auto-accept invitations from a trusted domain

1. iCalendar Extract parses the incoming email.
2. Decision: {{event.organizer.email}} ends with @mycompany.com?
3. iCalendar Respond with action: accept, attendeeEmail: agenda@floogos.com.
4. Send Mail to {{to}}, subject {{subject}}, attaching {{ics}} as {{filename}}.

Propose a new time decided by an AI agent

An agent (or any logic) resolves the conflict and leaves {{nuevaFecha}} in the data:

action: counter
attendeeEmail: agenda@floogos.com
newStart: {{nuevaFecha}}
newEnd: {{nuevaFechaFin}}
comment: That slot is taken — proposing the next free one.

Notes

• The reply must come from the attendee’s own address for Google/Outlook to apply it to the calendar automatically.
• sequence is echoed from the invitation; if you answer an updated invitation, extract it again so the sequence matches.
• Times without Z are interpreted in the engine server’s timezone — prefer UTC (…Z) in newStart/newEnd.