create_event
Facts
Connectors.MicrosoftOutlookCalendar.functions.CreateEventMicrosoft Outlook CalendarInput parameters
Required input parameters
attendeesarrayRequiredUser IDs to be added as attendees of this event
"123abc-456def","789ghi-012jkl"end_timeslack#/types/timestampRequiredThe end time of the event, as a Unix timestamp
1710220715event_titlestringRequiredThe title of the event to be created
start_timeslack#/types/timestampRequiredThe start time of the event, as a Unix timestamp
1698681600timezonestringRequiredThe timezone of the event
America/Los_AngelesOptional input parameters
additional_attendeesarrayOptionalAdditional attendees
outlook_access_tokenslack#/types/credential/oauth2OptionalOutlook access token. See the authentication section for details.
Output parameters
Optional output parameters
event_urlstringOptionalEvent URL
Authentication
End-user authentication
User workflows that include a connector function relying on end-user authentication can only be started with a link trigger.
{
"microsoft outlook calendar_access_token": {
"credential_source": "END_USER"
}
}
End-user experience: User will be prompted to link their external account via OAuth when they first start the workflow that contains this connector.
Developer experience: Developer does not have to implement authentication in the app.
Usage info
First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:
{
"imports": {
"deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
"deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
"deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/"
}
}
Next, import Connectors at the top of your workflow's definition file:
import { Connectors } from "deno-slack-hub/mod.ts";
Finally, add the connector as a step in your workflow just like you would a Slack function.
SomeWorkflow.addStep(
Connectors.MicrosoftOutlookCalendar.functions.CreateEvent, {
//...
🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:
Workflow function X is referring to an unknown step output parameter YYou can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.