Appbricx
Docs
FeaturesPricingStart free

Get started

OverviewWhat Appbricx isQuickstart with a coding agentQuickstart with the builderCore concepts

Guides

Data and tablesAccess and rolesBusiness rulesSign-inCustom screensRealtime and topicsWorkflows, schedules and webhooksServer functionsAI in your appPaymentsFilesMessagesIntegrationsVerifyPublishing, domains and rollbackOperating your appExport and self-hostSelf-host install

Tutorials

Build a booking app with Claude CodeMulti-user todo listClient portalSlack on new sign-upTemplates

Reference

Reference homeFrontend SDKHTTP APIMCP toolsCLIIntegrations catalogContract formatAI key resolutionRun Appbricx locally

X (Twitter)

Create tweets, search content, and manage your presence on X (Twitter).

Social mediaOAuth2 actionsAll integrations

On this page
  1. Connect
  2. Call it from a workflow
  3. Actions (2)
  4. create-tweet
  5. create-reply
  6. Details

Connect

Auth type: OAuth (oauth2). Click Connect and approve access on the provider's page. Appbricx runs the OAuth flow (signed single-use state, PKCE where the provider supports it), stores the tokens encrypted and refreshes them before they expire.

Scopes requested: tweet.readtweet.writeusers.read

OAuth needs an OAuth app: the platform's when the operator configured one, or your own (admin panel, Integrations, Configure). You can also bring your own credentials.

  • In the editor: Backend panel, Integrations tab, then Connect. This connects it for the project.
  • For every project in a workspace: Workspace settings, Integrations.
  • Owners and admins choose which integrations members may connect in the admin panel (Integrations tab), and can attach their own OAuth app there.

Call it from a workflow

Pass the action name and its input. The call resolves with { success, output, error? }; a missing connection resolves with success false and the reason. See ctx.integrations.invoke and ctx.integrations.call.

Native workflow
// .workflow.js (native ctx)
export async function run(ctx) {
  const res = await ctx.integrations.invoke("twitter", "create-tweet", {
    "text": "<text>"
  });
  if (!res.success) throw new Error(res.error);
  ctx.log.info("X (Twitter) answered", { output: res.output });
}
defineWorkflow module
// defineWorkflow module (@app/sdk ctx)
import { defineWorkflow } from "@app/sdk";

export default defineWorkflow({
  id: "twitter-create-tweet",
  name: "X (Twitter): Create Tweet",
  description: "Calls X (Twitter) when a row is created.",
  trigger: { type: "entity_event", entity: "tickets", event: "created" },
  async run(ctx, event) {
    const res = await ctx.integrations.call("twitter", {
      "action": "create-tweet",
      "text": "<text>"
    }) as { success: boolean; error?: string };
    if (!res.success) throw new Error(res.error);
  },
});
From an app (connector proxy)
curl -X POST "$APP_ORIGIN/__appbricx/connector-proxy/twitter/create-tweet" \
  -H "Authorization: Bearer $APP_KEY" \
  -H "content-type: application/json" \
  -d '{"props":{"text":"<text>"}}'

Actions

create-tweetin catalog

Create Tweet. Create a tweet

InputTypeDescription
textrequiredlong textThe text of the tweet
image_1optionalfileAn image, video or GIF url or base64 to attach to the tweet
image_2optionalfileAn image, video or GIF url or base64 to attach to the tweet
image_3optionalfileAn image, video or GIF url or base64 to attach to the tweet

create-reply

Create Reply. Reply to a tweet.

InputTypeDescription
tweet_idrequiredlong textThe ID of the tweet to reply too.
textrequiredlong textThe text of the tweet
image_1optionalfileAn image, video or GIF url or base64 to attach to the tweet
image_2optionalfileAn image, video or GIF url or base64 to attach to the tweet
image_3optionalfileAn image, video or GIF url or base64 to attach to the tweet

Details

Id
twitter
Category
Social media
Tags
social, twitter, x, tweets, microblogging
Package
@activepieces/piece-twitter@0.3.3
Tier
Built in

On this page

  1. Connect
  2. Call it from a workflow
  3. Actions (2)
  4. create-tweet
  5. create-reply
  6. Details
Appbricx

The backend, runtime and hosting for apps your coding agent builds. On our cloud, in yours, or on your own servers.

Features

Coding agents and MCPVerify testingBuilder consolePostgres databaseData APIRealtimeRow-level securitySign-in and authPaymentsWorkflows and jobsAI in your appIntegrationsBackups and rollbackHosting and domainsSelf-host and exportAll features

Product

ShowcasePricingFor coding agentsTemplatesPrivate cloudBring your own AI keyFAQ

Compare

Appbricx vs SupabaseLovable alternativeBolt alternativeFor freelancersFor agencies

Resources

DocumentationReferenceBlogSupportContact

© 2026 Appbricx. All rights reserved.

TermsPrivacyCookiesAcceptable Use