import app from "../../topdesk.app.mjs";
export default {
key: "topdesk-create-incident",
name: "Create Incident",
description: "Creates a new incident. [See the documentation](https://developers.topdesk.com/explorer/?page=incident#/incident/createIncident)",
version: "0.0.1",
type: "action",
props: {
app,
callerLookupId: {
type: "string",
label: "Caller Lookup ID",
description: "Lookup value for filling in a registered caller's contact details (UUID). **Required** - you must specify either this field or provide caller details manually.",
propDefinition: [
app,
"personId",
],
},
status: {
type: "string",
label: "Status",
description: "Status of the incident. Can only be set by operators.",
optional: true,
options: [
"firstLine",
"secondLine",
"partial",
],
},
briefDescription: {
propDefinition: [
app,
"briefDescription",
],
},
request: {
propDefinition: [
app,
"request",
],
},
action: {
propDefinition: [
app,
"action",
],
},
actionInvisibleForCaller: {
propDefinition: [
app,
"actionInvisibleForCaller",
],
},
categoryId: {
propDefinition: [
app,
"categoryId",
],
},
subcategoryId: {
propDefinition: [
app,
"subcategoryId",
({ categoryId }) => ({
categoryId,
}),
],
},
callTypeId: {
propDefinition: [
app,
"callTypeId",
],
},
entryTypeId: {
propDefinition: [
app,
"entryTypeId",
],
},
externalNumber: {
propDefinition: [
app,
"externalNumber",
],
},
objectName: {
propDefinition: [
app,
"objectName",
],
},
locationId: {
propDefinition: [
app,
"locationId",
],
},
branchId: {
propDefinition: [
app,
"branchId",
],
},
mainIncidentId: {
type: "string",
label: "Main Incident ID",
description: "Main incident UUID, required for creating a partial incident. Can only be set by operators.",
optional: true,
},
impact: {
propDefinition: [
app,
"impactId",
],
},
urgency: {
propDefinition: [
app,
"urgencyId",
],
},
priority: {
propDefinition: [
app,
"priorityId",
],
},
duration: {
propDefinition: [
app,
"durationId",
],
},
targetDate: {
propDefinition: [
app,
"targetDate",
],
},
slaId: {
propDefinition: [
app,
"slaId",
],
},
onHold: {
propDefinition: [
app,
"onHold",
],
},
operatorId: {
propDefinition: [
app,
"operatorId",
],
label: "Operator",
description: "The operator assigned to the incident. Can only be set by operators.",
optional: true,
},
operatorGroupId: {
propDefinition: [
app,
"operatorGroupId",
],
},
supplierId: {
propDefinition: [
app,
"supplierId",
],
},
processingStatusId: {
propDefinition: [
app,
"processingStatusId",
],
},
responded: {
propDefinition: [
app,
"responded",
],
},
responseDate: {
propDefinition: [
app,
"responseDate",
],
},
completed: {
propDefinition: [
app,
"completed",
],
},
completedDate: {
propDefinition: [
app,
"completedDate",
],
},
closed: {
propDefinition: [
app,
"closed",
],
},
closedDate: {
propDefinition: [
app,
"closedDate",
],
},
closureCodeId: {
propDefinition: [
app,
"closureCodeId",
],
},
majorCall: {
propDefinition: [
app,
"majorCall",
],
},
publishToSsd: {
propDefinition: [
app,
"publishToSsd",
],
},
optionalFields1: {
propDefinition: [
app,
"optionalFields1",
],
},
optionalFields2: {
propDefinition: [
app,
"optionalFields2",
],
},
},
annotations: {
readOnlyHint: false,
destructiveHint: false,
openWorldHint: true,
idempotentHint: false,
},
async run({ $ }) {
const {
app,
callerLookupId,
status,
briefDescription,
request,
action,
actionInvisibleForCaller,
categoryId,
subcategoryId,
callTypeId,
entryTypeId,
externalNumber,
objectName,
locationId,
branchId,
mainIncidentId,
impact,
urgency,
priority,
duration,
targetDate,
slaId,
onHold,
operatorId,
operatorGroupId,
supplierId,
processingStatusId,
responded,
responseDate,
completed,
completedDate,
closed,
closedDate,
closureCodeId,
majorCall,
publishToSsd,
optionalFields1,
optionalFields2,
} = this;
const idFields = [
{
value: callerLookupId,
key: "callerLookup",
},
{
value: categoryId,
key: "category",
},
{
value: subcategoryId,
key: "subcategory",
},
{
value: callTypeId,
key: "callType",
},
{
value: entryTypeId,
key: "entryType",
},
{
value: locationId,
key: "location",
},
{
value: branchId,
key: "branch",
},
{
value: mainIncidentId,
key: "mainIncident",
},
{
value: impact,
key: "impact",
},
{
value: urgency,
key: "urgency",
},
{
value: priority,
key: "priority",
},
{
value: duration,
key: "duration",
},
{
value: slaId,
key: "sla",
},
{
value: operatorId,
key: "operator",
},
{
value: operatorGroupId,
key: "operatorGroup",
},
{
value: supplierId,
key: "supplier",
},
{
value: processingStatusId,
key: "processingStatus",
},
{
value: closureCodeId,
key: "closureCode",
},
];
const response = await app.createIncident({
$,
data: {
status,
briefDescription,
request,
action,
actionInvisibleForCaller,
externalNumber,
targetDate,
onHold,
responded,
responseDate,
completed,
completedDate,
closed,
closedDate,
majorCall,
publishToSsd,
optionalFields1,
optionalFields2,
...(objectName && {
object: {
name: objectName,
},
}),
...idFields.reduce((acc, {
value, key,
}) => ({
...acc,
...value && {
[key]: {
id: value,
},
},
}), {}),
},
});
$.export("$summary", `Successfully created incident with ID \`${response.id}\``);
return response;
},
};
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.