SOCIAL MEDIA

Discord /rsvp slash command with Outlook calendar invite

Lets members RSVP to an event via a /rsvp slash command, captures their status (yes/maybe/no), and sends a matching Outlook calendar invitation or cancellation to their email.

CategorySocial Media
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • Trigger/rsvp slash command invokedDiscordDiscord
  • ActionUpsert RSVP status in attendee tablePostgreSQLPostgres
  • LogicBranch on yes / maybe / no
  • ActionSend or cancel Outlook calendar inviteOutlook
  • OutputReply with confirmation in DiscordDiscordDiscord

What it does

This workflow handles a /rsvp slash command in Discord. A member picks an event and a status of yes, maybe, or no. The flow records the response and sends the appropriate Outlook calendar action: a confirmed invite for yes, a tentative invite for maybe, or a cancellation for no.

When to use it

Use this for communities that prefer explicit command-based RSVPs over emoji reactions and whose members live in Outlook. It gives each attendee a real calendar entry that reflects their commitment level.

How it works

  1. 1A Discord slash-command interaction triggers the workflow with the chosen event and status.
  2. 2The flow upserts the member's RSVP status in the attendee table.
  3. 3A branch routes on the status value.
  4. 4For yes or maybe it creates or updates an Outlook event invitation (busy or tentative); for no it cancels any existing invite.
  5. 5It replies in Discord with an ephemeral confirmation of the recorded status.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.