The calendar and scheduling component of Outlook that is fully integrated with email, contacts, and other features
Emit new event when a new Calendar event is created
Emit new event when a Calendar event is updated
Emit new event when a Calendar event is upcoming, this source is using reminderMinutesBeforeStart
property of the event to determine the time it should emit.
Create an event in the user's default calendar. See the documentation
Continue workflow execution only if a condition is met
Delete an event in the user's default calendar. See the documentation
Update an event in the user's default calendar. See the documentation
The Microsoft Outlook Calendar API provides programmatic access to a user's calendar events, allowing for the creation, retrieval, update, and deletion of events within Outlook calendars. With Pipedream, you can integrate these calendar operations into workflows that automate tasks involving scheduling, event management, and coordination with other services. Whether it's triggering actions when new events are created, syncing calendar events with other scheduling tools, or managing attendees, Pipedream's serverless platform enables you to build custom automations with minimal overhead.
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
microsoft_outlook_calendar: {
type: "app",
app: "microsoft_outlook_calendar",
}
},
async run({steps, $}) {
return await axios($, {
url: `https://graph.microsoft.com/v1.0/me`,
headers: {
Authorization: `Bearer ${this.microsoft_outlook_calendar.$auth.oauth_access_token}`,
},
})
},
})
The Filter API in Pipedream allows for real-time data processing within workflows. It's designed to evaluate data against predefined conditions, enabling workflows to branch or perform specific actions based on those conditions. This API is instrumental in creating efficient, targeted automations that respond dynamically to diverse datasets. Using the Filter API, you can refine streams of data, ensuring that subsequent steps in your Pipedream workflow only execute when the data meets your specified criteria. This cuts down on unnecessary processing and facilitates the creation of more intelligent, context-aware systems.
export default defineComponent({
async run({ steps, $ }) {
let condition = false
if (condition == false) {
$.flow.exit("Ending workflow early because the condition is false")
} else {
$.export("$summary", "Continuing workflow, since condition for ending was not met.")
}
},
})