import utils from "../../common/utils.mjs";
import frontApp from "../../frontapp.app.mjs";
export default {
key: "frontapp-reply-to-conversation",
name: "Reply To Conversation",
description: "Reply to a conversation by sending a message and appending it to the conversation. [See the docs here](https://dev.frontapp.com/reference/post_conversations-conversation-id-messages).",
version: "0.0.2",
type: "action",
props: {
frontApp,
conversationId: {
propDefinition: [
frontApp,
"conversationId",
],
},
tagIds: {
propDefinition: [
frontApp,
"tagIds",
],
optional: true,
description: "List of all the tag IDs replacing the old conversation tags",
},
authorId: {
propDefinition: [
frontApp,
"teammateId",
],
label: "Author ID",
description: "ID of the teammate on behalf of whom the answer is sent",
},
senderName: {
type: "string",
label: "Sender Name",
description: "Name used for the sender info of the message",
optional: true,
},
subject: {
type: "string",
label: "Subject",
description: "Subject of the message for email message",
optional: true,
},
body: {
type: "string",
label: "Body",
description: "Body of the message",
},
text: {
type: "string",
label: "Text",
description: "Text version of the body for messages with non-text body",
optional: true,
},
attachments: {
propDefinition: [
frontApp,
"attachments",
],
},
optionsTagIds: {
propDefinition: [
frontApp,
"tagIds",
],
optional: true,
description: "List of tag names to add to the conversation (unknown tags will automatically be created)",
},
optionsIsArchive: {
type: "boolean",
label: "Is Archive",
description: "Archive the conversation right when sending the message (Default: true)",
optional: true,
},
to: {
propDefinition: [
frontApp,
"to",
],
},
cc: {
propDefinition: [
frontApp,
"cc",
],
},
bcc: {
propDefinition: [
frontApp,
"bcc",
],
},
},
async run({ $ }) {
const {
conversationId,
authorId,
senderName,
subject,
body,
text,
optionsIsArchive,
} = this;
const to = utils.parse(this.to);
const cc = utils.parse(this.cc);
const bcc = utils.parse(this.bcc);
const tagIds = utils.parse(this.optionsTagIds);
const attachments = utils.parse(this.attachments);
const hasAttachments = utils.hasArrayItems(attachments);
const hasCc = utils.hasArrayItems(cc);
const hasBcc = utils.hasArrayItems(bcc);
const data = utils.reduceProperties({
initialProps: {
to,
body,
},
additionalProps: {
cc: [
cc,
hasCc,
],
bcc: [
bcc,
hasBcc,
],
sender_name: senderName,
subject,
author_id: authorId,
body,
text,
options: {
tag_ids: tagIds,
archive: optionsIsArchive ?? true,
},
attachments: [
attachments,
hasAttachments,
],
},
});
const args = utils.reduceProperties({
initialProps: {
conversationId,
data,
},
additionalProps: {
headers: [
{
"Content-Type": "multipart/form-data",
},
hasAttachments,
],
},
});
await this.frontApp.replyToConversation(args);
$.export("$summary", `Successfully updated conversation with ID ${conversationId}`);
return conversationId;
},
};
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.