Post Multiple Statuses with Mastodon API

Pipedream makes it easy to connect APIs for Mastodon and 2,400+ other apps remarkably fast.

Trigger workflow on

HTTP requests, schedules and app events

Next, do this

Post Multiple Statuses with the Mastodon API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

Create a workflow to Post Multiple Statuses with the Mastodon API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the Post Multiple Statuses action
1. Connect your Mastodon account
2. Configure Statuses
3. Optional- Configure In Reply To ID
4. Optional- Configure Sensitive
5. Optional- Configure Spoiler Text
6. Optional- Select a Visibility
7. Optional- Configure Scheduled At
Select a trigger to run your workflow on HTTP requests, schedules or app events
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Post Multiple Statuses with Mastodon API on New Requests from HTTP / Webhook API

HTTP / Webhook + Mastodon

Try it

Post Multiple Statuses with Mastodon API on New Submission from Typeform API

Typeform + Mastodon

Try it

Post Multiple Statuses with Mastodon API on New Submission (Instant) from Jotform API

Jotform + Mastodon

Try it

Post Multiple Statuses with Mastodon API on New Custom Webhook Events from Stripe API

Stripe + Mastodon

Try it

Post Multiple Statuses with Mastodon API on New Scheduled Tasks from Pipedream API

Pipedream + Mastodon

Try it

Details#

This is a pre-built, source-available component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Post Multiple Statuses on Mastodon

Description:Publish multiple statuses with the given parameters, the subsequent statuses will be posted as a reply of of the first status. [See the documentation](https://docs.joinmastodon.org/methods/statuses/#create)

Version:0.0.2

Key:mastodon-post-multiple-statuses

View on GitHub

Code#

import mastodon from "../../mastodon.app.mjs";
import { VISIBILITY_OPTIONS } from "../../common/constants.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  key: "mastodon-post-multiple-statuses",
  name: "Post Multiple Statuses",
  description: "Publish multiple statuses with the given parameters, the subsequent statuses will be posted as a reply of of the first status. [See the documentation](https://docs.joinmastodon.org/methods/statuses/#create)",
  version: "0.0.2",
  type: "action",
  props: {
    mastodon,
    statuses: {
      type: "string[]",
      label: "Statuses",
      description: "Array of statuses to be published in sequence; each status must be fewer than 500 characters long.",
    },
    inReplyToId: {
      type: "string",
      label: "In Reply To ID",
      description: "ID of the status being replied to, if the status is a reply.",
      optional: true,
    },
    sensitive: {
      type: "boolean",
      label: "Sensitive",
      description: "Mark the status and attached media as sensitive. The default is false.",
      optional: true,
      default: false,
    },
    spoilerText: {
      type: "string",
      label: "Spoiler Text",
      description: "Text to be shown as a warning or subject before the actual content. Statuses are generally collapsed behind this field.",
      optional: true,
    },
    visibility: {
      type: "string",
      label: "Visibility",
      description: "Set the visibility of the posted status to `public`, `unlisted`, `private`, or `direct`.",
      options: VISIBILITY_OPTIONS,
      optional: true,
    },
    scheduledAt: {
      type: "string",
      label: "Scheduled At",
      description: "ISO 8601 DateTime at which to schedule a status. Must be at least 5 minutes in the future.",
      optional: true,
    },
  },
  methods: {
    validateStatuses(statuses) {
      for (const status of statuses) {
        if (status.length > 500) {
          throw new ConfigurationError("Each status must be fewer than 500 characters long.");
        }
      }
    },
  },
  async run({ $ }) {
    const { statuses } = this;
    let { inReplyToId } = this;
    this.validateStatuses(statuses);

    const results = [];
    for (const status of statuses) {
      const data = {
        status,
        in_reply_to_id: inReplyToId,
        sensitive: this.sensitive,
        spoiler_text: this.spoilerText,
        visibility: this.visibility,
        scheduled_at: this.scheduledAt,
      };
      results.push(
        await this.mastodon.postStatus({
          $,
          data,
        }),
      );
      if (!inReplyToId) {
        inReplyToId = results[0].id;
      }
    }
    $.export("$summary", `Successfully posted ${statuses.length} statuses.`);
    return results;
  },
};

Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Mastodon	`mastodon`	`app`	This component uses the Mastodon app.
Statuses	`statuses`	`string[]`	Array of statuses to be published in sequence; each status must be fewer than 500 characters long.
In Reply To ID	`inReplyToId`	`string`	ID of the status being replied to, if the status is a reply.
Sensitive	`sensitive`	`boolean`	Mark the status and attached media as sensitive. The default is false.
Spoiler Text	`spoilerText`	`string`	Text to be shown as a warning or subject before the actual content. Statuses are generally collapsed behind this field.
Visibility	`visibility`	`string`	Select a value from the drop down menu:`publicunlistedprivatedirect`
Scheduled At	`scheduledAt`	`string`	ISO 8601 DateTime at which to schedule a status. Must be at least 5 minutes in the future.