decline a specific outlook invitation after your review
free the calendar slot without making up an excuse. the bot finds the outlook invitation and declines with your words, optionally proposing another time.
outlook emails the organiser by default. dusk classes this as a write, so sending approval does not hold it. tell the bot to ask before declining.

decline calendar event, in plain words
say no to the meeting you actually mean. name the date and organiser, especially when the title repeats. the bot finds the occurrence and can include your explanation or a proposed start and end time.
choose whether outlook should email the organiser; it sends a response by default. a proposed slot still needs a separate availability lookup and the other person's agreement.
a routine to copy
paste this into a chat with your bot
at 16:55 every tuesday, read next week's outlook invitations for supplier demonstrations that overlap another calendar event. show each title, organiser, date and clash here.
propose the explanation "thank you for the invitation; i will not be attending this session." ask me before changing any response. decline only the occurrence i approve and send only that explanation. report the result here. never invent reasons or propose another time without my start and end dates.- when
- tuesdays at 16:55
- needs
- outlook with read and write for event lookup and declines, including calendar write permission
what comes back looks like this (an example)
decline proposal
- zoe's supplier demonstration, friday 11:00
- organiser: caraway optics
- explanation: thank you for the invitation; i will not be attending this session.
email the organiser only after you agree. invitation unchanged.good jobs for it
- decline a supplier demo you have decided to skip
- turn down an optional workshop with your chosen explanation
- decline a clashing meeting and propose a specific alternative
- decline quietly when you choose not to email the organiser
before it runs
dusk bot counts Decline calendar event as a change: it alters something in Outlook, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Outlook asks for to run it: Calendars.ReadWrite.
how to start
- connect outlook. allow read and write for calendar lookup and declines.
- name the exact meeting, date and occurrence if it repeats.
- choose the explanation and whether to email the organiser. ask for review before declining.
- open the invitation after the first decline and read its response status. Pause if it picked the wrong one.
limits worth knowing
- put the pause before the decline. this action can email the organiser, but dusk classes it as a write. sending controls do not hold it.
- use the date and organiser to pick an occurrence. repeating titles can hide different meetings.
- give both ends of the new slot. look up availability separately; a proposed time reserves nothing.
- outlook accepted the request. the organiser still has to read it. success says nothing about their agreement.
the details it works from
| input | required | what it is |
|---|---|---|
event_id | yes | The unique identifier of the calendar event to decline. |
comment | no | Optional text message to include in the response to the event organizer explaining the decline. |
send_response | no | If true, a decline response is sent to the organizer; if false, no response is sent. |
proposed_new_time | no | A time period with start and end times. |
from composio's catalog for Outlook (action OUTLOOK_DECLINE_EVENT, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- connect outlook with calendar lookup and decline allowed
- ask for one invitation's title, organiser and exact date
- choose the response wording and whether to notify the organiser
- ask the bot to wait for your agreement before declining
quick checklist
- the date and organiser match the invitation
- you chose whether to email a response
- the reason contains no invented details
- any proposed time has a start, end and separate availability lookup
mistakes people make
assuming sending approval covers declines
put "ask me before you decline anything" in the routine.
rejecting a whole series by a familiar title
match the date and organiser to the occurrence you want to decline.
questions
can it decline without sending an email response?
yes. ask it to decline without sending a response. otherwise outlook tells the organiser.
does the bot ask before declining an invitation?
tell it to ask before declining. dusk classes the action as a write, so the review step belongs in the routine.
can it suggest another time while declining?
yes, with a start and end time. look up availability separately. the proposal does not book that slot for everyone.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
find the outlook appointment you can only partly remember
an outlook bot for the mail around your meetings
start a new outlook email as a draft
put the next step in your microsoft to do list
retrieve the actual file attached to an outlook email
find outlook meeting options that fit your attendees