Microsoft SharePoint
Tasks that interact with SharePoint document libraries for file operations.
Tasks that integrate Microsoft 365 and Dynamics 365 services.
Authenticate with Microsoft Graph or Azure AD (tenant, client ID/secret or certificate) once and reuse the connection to manage Outlook mail, OneDrive/SharePoint files, Dataverse entities, and Business Central financials directly from Kestra workflows.
Interact with Microsoft Teams, OneDrive, SharePoint, Outlook, and Dynamics 365 from Kestra flows.
Teams (teams.TeamsIncomingWebhook, teams.TeamsExecution): set url to a Teams incoming webhook URL. Create one in Teams under channel settings → Connectors. Store it in a secret.
OneDrive, SharePoint, and Outlook tasks authenticate via Microsoft Graph API using an Azure AD app registration. Set tenantId, clientId, and clientSecret on each task (or use pemCertificate instead of clientSecret for certificate-based auth).
Defender tasks (defender.*) use the same Microsoft Graph app registration with application permissions: SecurityAlert.Read.All or SecurityAlert.ReadWrite.All for alerts, SecurityIncident.Read.All or SecurityIncident.ReadWrite.All for incidents, and ThreatHunting.Read.All for advanced hunting. Grant admin consent after adding them.
Dynamics 365 Dataverse and Business Central tasks use the same Azure AD app registration pattern — set tenantId, clientId, and clientSecret (or pemCertificate). Grant the service principal the Dynamics CRM user permission for Dataverse tasks, or the Financials.ReadWrite.All permission for Business Central tasks.
teams.TeamsIncomingWebhook sends a message as a step within a flow — set payload to a JSON body in the Teams adaptive card format. teams.TeamsExecution sends a structured execution summary and is designed for use with a Flow trigger in a dedicated monitoring namespace that watches other namespaces for failures.
teams.adaptivecards tasks send Adaptive Cards via the Microsoft Graph API instead of a webhook, using the same Azure AD app registration (tenantId, clientId) as the other tasks in this plugin, letting you target any channel or user by ID and get back the created message ID. adaptivecards.Send posts a card to a Teams channel: set teamId, channelId, and card (the Adaptive Card JSON, rendered as a Pebble template). adaptivecards.SendToUser resolves (creating if needed) the 1: 1 chat between the authenticated identity and a target user and posts the card there: set card plus exactly one of userId or userEmail.
Both adaptivecards tasks need DELEGATED (acting-as-user) authentication: set username and password instead of clientSecret/pemCertificate so the task signs in with Resource Owner Password Credentials (ROPC) as a real user or service account (one without MFA enforced, since ROPC has no interactive step). This also requires the Azure AD app registration to have "Allow public client flows" enabled, plus the delegated Graph permission for the operation: ChannelMessage.Send for Send, Chat.ReadWrite for SendToUser. SendToUser uses username directly as the authenticated caller's identity (no User.Read scope needed) to add it as the second member of the 1: 1 chat. App-only clientSecret/pemCertificate credentials are rejected by Microsoft Graph with an HTTP 403 for both tasks: sending a channel or chat message is not supported with application permissions alone.
oneshare tasks manage files in OneDrive: Upload and Download move files between Kestra internal storage and OneDrive; Create creates folders; Delete removes items; List queries a drive; Export converts OneDrive-hosted Office files to a downloadable format. oneshare.Trigger polls for file changes (creates and updates) in a OneDrive or SharePoint folder using Microsoft Graph delta links.
sharepoint tasks manage files in SharePoint document libraries: Upload, Download, Create, Delete, List, Export, and Move. Set siteId and driveId on SharePoint tasks to target the correct site and library.
outlook tasks interact with email: Send sends a message, Get reads a message by ID, List queries the mailbox. outlook.MailReceivedTrigger polls for new messages and starts one execution per batch.
defender tasks work with Microsoft Defender XDR through the Microsoft Graph security API. defender.ListAlerts and defender.ListIncidents list alerts and incidents with an optional raw OData filter plus severity and status shortcuts, top (1 to 2000, default 100) and fetchType (FETCH, FETCH_ONE or STORE, default FETCH). ListIncidents can also expandAlerts. defender.GetAlert and defender.GetIncident read one item by ID. defender.UpdateAlert sets status, classification, determination or assignedTo. defender.UpdateIncident also takes customTags and a comment, which is added with a separate call. Closed-set properties use enums such as HIGH, IN_PROGRESS and FALSE_POSITIVE, mapped to the Microsoft Graph wire values automatically. Only the properties you set are sent.
defender.HuntingQuery runs a KQL advanced hunting query over timespan (default P7D) and returns typed rows plus the query schema, stored in internal storage by default (fetchType: STORE). Validate inputs interpolated into KQL. The device-name example uses an input validator that rejects quotes and other query syntax.
dynamics365.dataverse tasks interact with the Dataverse Web API (OData v9.2) — all require orgUrl (your Dataverse organization URL, e.g. https://myorg.api.crm.dynamics.com). dataverse.Query fetches entity records — set entitySetName (required); optionally set filter (OData $filter expression), select (comma-separated fields), top (default 100), and fetchType (FETCH, FETCH_ONE, or STORE, default FETCH). dataverse.Upsert creates or updates a record by GUID — set entitySetName, recordId, and record (a map of field values, all required). dataverse.Delete permanently removes a record — set entitySetName and recordId (both required).
dynamics365.businesscentral tasks interact with the Business Central API v2.0 — all require environment (e.g. production or sandbox). businesscentral.ListCompanies returns all companies in the environment. The remaining tasks also require companyId (the company GUID): GetCustomer and GetInvoice fetch a single record by customerId or invoiceId; CreateCustomer and CreateInvoice create records from a customer or invoice map and output the new record's ID; ListItems lists inventory items with optional filter and top (default 100).
defender.Trigger polls Defender alerts (resource: ALERTS, default) or incidents (resource: INCIDENTS) and starts one execution with the new or updated items, stored as an ION file in internal storage and exposed as trigger.uri and trigger.count. Use ForEachItem to process them. The first poll only records a starting point, so existing items are not replayed. Each poll re-reads a lookback window (default PT5M) and deduplicates by item ID in the trigger state, so items indexed late are not missed or fired twice. on accepts CREATE, UPDATE or CREATE_OR_UPDATE (default). on: CREATE polls on createdDateTime. on: UPDATE only fires for items already seen by the trigger.