Wiresk

Wiresk

X (Twitter) – Connection & settings

Estimated reading time: 5 min
X twitter banner

X, formerly Twitter, is one of the largest social media platforms where users can share short messages, images, and videos known as “tweets” (officially called “posts”) to interact with their followers.

X integration with Wiresk allows businesses to manage their content directly through the platform, enhancing engagement and communication. With this integration, users can create and publish tweets, delete tweets, and even retrieve information about your own X account.

A connection to your X account is needed so we can sync it with our platform.

There are two ways to connect your app to Wiresk:

  • In “My apps” section, where you can manage your connections (select or create your group first to get access to this section, refer to the Group system ).
  • While building your Flow, you can easily establish a connection to your app directly within the Flow builder. This can be done during the setup of either a Trigger or a Method.

This guide explains how to set up a connection in “My apps” section, which is essentially the same process as creating one on-the-go.

  • Register to X developer Portal.
  • Access to your dashboard and click on the “+ Add App” button. (or select your project app auto generated).
Screenshot of the X (formerly Twitter) Developer Portal dashboard. The interface displays a sidebar on the left with menu options: Dashboard, Projects & Apps, Products (marked as "NEW"), and Account. The main section shows a "Projects" area with a default project title. A prominent black "+ Add App" button is outlined in red, allowing users to create a new app within the project.
  • On the App creation page, name your app.
“Name your App” screen in the X Developer Portal with a text field filled with “Wiresk test” and navigation showing step 1 of 2 (App name).
  • On the page “Keys & Tokens“, your API Key and API Key Secret are displayed.
  • Copy both of them and save it in a safe place.
  • Then click on App settings.
“Here are your keys & tokens” screen in the X Developer Portal displaying API Key, API Key Secret, and Bearer Token fields with copy buttons, plus navigation to “App settings.”
  • In the Settings tab, under User authentication settings section, click on Set up to give permissions to your app.
X Developer Portal “App details” page for “Wiresk test” under “Projects & Apps.” Shows app name, app ID, description, and a section for “User authentication settings” with a “Set up” button.
  • Under App permissions, select Read and write.
  • Under Type of App, select Web App, Automated App or Bot.
“User authentication settings” page in the X Developer Portal. “Read and write” permissions are selected along with “Web App, Automated App or Bot” as the app type.
  • Under App info, fill in:
    • Callback URI / Redirect URL : https://api.wiresk.com/api/auth/callback
    • Website URL: https://api.wiresk.com/
“App info” screen in the X Developer Portal showing required fields for Callback URL (set to a Wiresk API endpoint) and Website URL, plus optional fields for organization name, organization URL, terms of service, and privacy policy.
  • Click Save, then confirm the changes on the prompted screen.
  • On the next screen, the Client ID and Client Secret will be displayed. Wiresk doesn’t require them, but you may choose to save them for future reference.
  • Click on Done.
  • Now, select Key and tokens tab, then under Authentication Tokens > Access Token and secret, Click on Generate.
X Developer Portal “Keys and tokens” tab for “Wiresk test.” Shows sections for Consumer Keys, Authentication Tokens, and OAuth 2.0 credentials with “Generate” and “Regenerate” options.
  • On the prompted screen, your Access Token and Access Token Secret are displayed.
  • Copy both of them and save it in a safe place for Wiresk connection settings.
  • Go back to Wiresk for the next steps.
Confirmation screen displaying Access Token and Access Token Secret values with copy buttons and a “Yes, I saved them” button.
  • On your Wiresk’s Dashboard, select your Group.
  • On the left panel, go to “My apps” and select Screenshot 2025 04 08 at 9.58.41 in the morning X (Twitter) - Connection & settings
  • Search the app name in the search field or select it in the apps list.
Animated image GIF, showing the step of how to create an app connection. First, select the group then select My Apps tab, and click on the "+ create" button.

On the connection settings panel:

  • Give a Name to the connection.
  • Enter your X credentials saved from the previous steps:
    • Consumer Key (API Key).
    • Consumer Secret (API Key Secrete).
    • Access Token.
    • Token Secret.
  • Click on “Create App” button.
A user interface screen for connecting an X app in Wiresk, showing required fields with red arrows pointing to them. The fields include: Name, Consumer Key, Consumer Secret, Access Token, and Token Secret. There are buttons labeled “Test” and “Create” at the bottom right of the screen. The layout is minimalistic with a sidebar on the left labeled “My Apps” and a “+ Create” button.

Voila! Your X app connection is ready. You can now use it to build your Flows.

Now that your app is linked to Wiresk, you’re ready to start building Flows.

Simple steps to create a Flow ↓
  • Select your Group, then on the Flow management screen click on “Create Flow”.
  • On the new screen, name the new Flow.
GIF animated screen of Wiresk, showing the way to create a new Flow.

Add a Trigger that will start your Flow

Flows can be executed by multiple Triggers, depending on the desired workflow. For example, you could use scheduled Triggers with different recurrence rules alongside a Webhook Trigger for immediate, event-driven runs of the Flow. If you choose to “Run Once“, the Flow will execute using only one Trigger and its sample data.
  • Click on the (+) button to open the Trigger settings side panel.
  • On the settings side panel, click on the “+ Add” button.
Screenshot of the Wiresk side panel titled “Trigger.” The panel shows a section labeled “All Triggers” with a blue “+ Add” button for inserting a new Trigger.
  • On the Trigger selection screen, search your app or select it from the list below the screen.
Screenshot of Wiresk Trigger setting screen. Red arrows shows that you can wether search your app in the search or or select it in the list below.
  • Select your preferred Trigger on the next screen and customize its settings.
As mentioned in “How to connect your app to Wiresk” above, during your Trigger settings, you can create a new connection to your apps at this stage.

Add a Method that will execute a task

The Method will perform a specific task on a particular app or service you’ve connected to Wiresk like get info or send emails.

You can add at least 1 or multiple Methods for complex Flows (a maximum of 255 Methods).
  • On the Flow builder, select the (+) plus button next the Trigger button.
  • Search or scroll down to select the app that will perform a task.
  • Configure the Methods settings, refer to it documentation in our Help Center.
Screenshot of Wiresk Flow Builder with a Flow named “Flow Example.” The canvas shows a Gmail Trigger on the left connected to an empty step placeholder marked with a plus icon in the center. On the right, the panel lists available apps and tools. A search bar is displayed at the top of the panel for filtering apps. Red arrows highlight the empty step placeholder, the search bar, and items in the app list.

Add Wiresk Tools to your Flow

If you want to build a complex Flow, Wiresk offers a selection of tools at your disposal. Refer to Wiresk’s Tools

To add Tools in your Flow, Follow the same step as adding the Methods.

  • On the Flow builder screen, click on the plus button (+) then just click on the “Tool” tab and select the Tool that you want to add.
Screenshot of Wiresk Flow Builder showing a Gmail Trigger connected to an empty Method placeholder. A red arrow points to the empty step circle with a plus sign where the next action will be added. On the right side, the “Tool” tab is selected in the panel. Another red arrow highlights the “Tool” tab label at the top. A search bar is shown above a list of available tools.
You can refer to “How to Create a Flow” tutorial for more detailed instructions, including step-by-step guidance on mapping and configuration.

What your automation will do…

X

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name*Create Tweet
Connection*Select your connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method. ↓

Geo Location:

Place ID: Place being attached to the Tweet for geo location.

How to Get a Place ID for Geo Localization:

  1. Use Twitter’s GET /2/tweets/search/recent or GET /2/tweets/search/all (Paid plan). Search tweets with a location filter, then extract the place_id from the matching tweet’s geo object.
  2. Use Twitter’s Deprecated v1.1 geo/search endpoint (Still works, but limited). This endpoint lets you search for places and returns their place_id.

Poll:

Duration of the poll in minutes*: If you post a poll, specify how long in minutes it will accept votes. Required range: 5 <= x <= 10080

Options*: Choices for the poll. Option limit to 2 - 4 elements.

  • Value*: What the options contain.

Quote Tweet ID:

ID of retweet post with comment.

The Quote Tweet ID is the string of numbers at the end of the Tweet URL.

Reply:

In Reply to tweet ID: Unique identifier of the Tweet being replied to.

Exclude Reply User ID:

  • User ID*: User ID of accounts to be excluded from the reply Tweet.

Reply Setting:

Reply Setting: Specify who can reply to the Tweet
Possible values: following, mentionedUsers, subscribers

Text*:

The content you want to post. Enter it manually or map it from Trigger or previous step responses.

Direct message deep link:

Link that takes the conversation from the public timeline to a Direct Message.

Refer to X Developer documentation to get more information about deep linking.

For super follower only:

Only show Tweet to super followers.
Possible values: True – False

Media:

Media information being attached to created Tweet. This is mutually exclusive from Quote Tweet Id, Poll, and Card URI.

+ Add Field ↓
Additional fields to configure the Media ↓

Media ID*

Identifier of a media in a Tweet. Refer to X Developer documentation to get more information about identifying media.

Required: 1 - 4 elements

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first user.

Media ID*:

The unique identifier of this Media.

Tagged User

A list of User Ids to be tagged in the media for created Tweet.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first user.

User ID*:

Maximum length: 10

Unique identifier of this User. This is returned as a string in order to avoid complications with languages and tools that cannot handle large integers.

⚠️ Wiresk’s current  “Create Tweet” Method (API v2) does not yet support direct media upload. To get a media ID, you must first upload the media to Twitter using the Media Upload API, which returns the media_id. This process requires using Twitter API v1.1, which is only available with a paid plan.

Sample response 
{
  "id": "1962788628813488286",
  "text": "Create Tweet with Wiresk",
  "edit_history_tweet_ids": [
    "1962788628813488286"
  ]
}

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name*Delete Tweet
Connection*Select your connection or create one.

Map Fields

Tweet ID*

ID of the Tweet to be deleted. Manually enter it or map it from Trigger or previous step responses.

How to get the Tweet ID:

  • From the Method response “Create Tweet“.
  • From a Tweet URL, the numbers at the end of the URL.
    • Example: https://twitter.com/wiresk/status/1234567890123456789 . So the tweet ID is the number after /status/: 1234567890123456789
Sample response 
{
  "deleted": true
}
X

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name*Get User
Connection*Select your connection or create one.
Response example 
{
  "name": "Wiresk user",
  "most_recent_tweet_id": "1952300433470292122",
  "verified_type": "none",
  "description": "",
  "verified": false,
  "id": "1945307415957962752",
  "username": "wireskO52984",
  "public_metrics": {
    "followers_count": 1,
    "following_count": 4,
    "tweet_count": 3,
    "listed_count": 0,
    "like_count": 0,
    "media_count": 0
  },
  "profile_image_url": "https://pbs.twimg.com/profile_images/194530749580f062736/3eYcdSdx_normal.png",
  "created_at": "2025-07-16T02:20:23.000Z",
  "protected": false
}

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.

Important 01 X (Twitter) - Connection & settings

Going further Copy Link

Explore the full Wiresk User Guide to learn more.

Looking for an integration that’s not yet available? Submit a request to our team, we’ll do our best to support your needs.