How to Resolve Configuration Error with Twitter Integration in X Using Oauth API Keys?

user-1 · February 7, 2024, 10:01pm

This topic was automatically generated from Slack. You can find the original thread here.

Hi folks! I need help with the X/Twitter integration. I have a paid developers license for Twitter. My Twitter account is connected using my Oauth API keys.

When I got to create a trigger… ANY trigger for Twitter, I get this error:

Configuration Error
A problem that indicates this request is invalid. If your request takes a POST body, ensure the contents is valid JSON and matches the OpenAPI spec. {"errors":[{"parameters":{"ids":[]},"message":"The ids query parameter can not be empty"}],"title":"Invalid Request","detail":"One or more parameters to your request was invalid.","type":"https://api.twitter.com/2/problems/invalid-request"}

The error is clear, but no where in the config of the trigger can I add any parameters. Am I missing something?

user-1 · February 7, 2024, 10:01pm

It might be that Twitter’s API has changed, or there was an issue in the latest version of that source.

It looks like it was updated 3 weeks ago:

github.com

PipedreamHQ/pipedream/blob/master/components/twitter/sources/new-mention-received-by-user/new-mention-received-by-user.ts

import { defineSource } from "@pipedream/types";
import common from "../common/base";
import { getTweetSummary as getItemSummary } from "../common/getItemSummary";
import { getTweetFields } from "../../common/methods";
import { GetUserMentionsParams } from "../../common/types/requestParams";
import {
  DOCS_LINK, MAX_RESULTS_PER_PAGE,
} from "../../actions/list-mentions/list-mentions";
import { Tweet } from "../../common/types/responseSchemas";
import cacheUserId from "../common/cacheUserId";

export default defineSource({
  ...common,
  key: "twitter-new-mention-received-by-user",
  name: "New Mention Received by User",
  description: `Emit new event when the specified User is mentioned in a Tweet [See the documentation](${DOCS_LINK})`,
  version: "0.0.5",
  type: "source",
  props: {
    ...common.props,

This file has been truncated. show original

user-1 · February 7, 2024, 10:01pm

You can report bug reports on actions and triggers here in our public Pipedream Github Repository:

A Pipedream team developer or community member will investigate and make a new version to attempt to fix it if they can reproduce the bug.

All Pipedream triggers and actions are open source, so you can also contribute your own fix if you’d like.

Learn about how to develop new and modify existing components here: Overview

user-1 · February 7, 2024, 10:01pm

Thanks, This is what I thought.

Is there an SLA on bugs being reviewed? I did submit one. I only ask because I am under a time constraint on this initiative. If there is no SLA, I will need to explore other options.

user-1 · February 7, 2024, 10:01pm

Got it, does your workspace have a Business or Enterprise level subscription? We have a prioritized queue for Business and above level customers.

user-1 · February 7, 2024, 10:01pm

No, I am only an Advanced plan

user-1 · February 7, 2024, 10:01pm

Got it, I’ll see what I can do to help get it prioritized a bit higher.

But all of the Pipedream sources and actions are all open source.

You can fork the Pipedream repository and modify that component I linked above to deploy a private version of the trigger to your account if you’d like to fix the issue yourself.

user-1 · February 7, 2024, 10:01pm

Thanks for your help!

user-1 · February 7, 2024, 10:01pm

Sure thing, happy to

user-1 · February 7, 2024, 10:01pm

Hi Craig, I’m working on the fix right now - should be out shortly.

user-1 · February 7, 2024, 10:01pm

, can you give this a try again and remove, and re-add the source/action? Just pushed the fix and it should be working correctly now.

user-1 · February 7, 2024, 10:01pm

Thanks, I just realized my trim didn;'t catch it all.

user-1 · February 7, 2024, 10:01pm

Hi Craig! Thanks for flagging the issue yesterday. I’ve pushed a fix and the sources should be working now - can you remove the trigger, re-add it and let me know if this works for you now? Please be aware that Twitter imposes very strict rate limits depending on the API endpoint being used (Rate limits | Docs | Twitter Developer Platform), so I would advise being more conservative when setting up the polling trigger (i.e., poll every 15 minutes or less frequently to avoid rate limit issues), depending on your Twitter subscription plan.

user-1 · February 7, 2024, 10:01pm

It is now working! Thanks !!

user-1 · February 7, 2024, 10:01pm

Craig, just a heads up - if you run into any other Twitter API related errors using our components, please raise them again here in this thread.

I’ve been going back and testing each of the components, and noticing that Twitter changed access to a few of their endpoints and didn’t update their documentation. For example, Followers and List Follows endpoints are no longer on Basic and Pro plan, but gated behind Enterprise tier. This is only shown on their changelog but not on their API docs page. I’ve submitted that feedback to their developer platform, but it’s unlikely to get fixed as their docs page is full of broken links and outdated info.

Just wanted to warn you ahead of time! I will be deprecating any of the components on our end that are no longer working as a result of the changes as I find them, as we don’t have a way to test Enterprise-only components on our side.

user-1 · February 7, 2024, 10:01pm

Appreciate the update, . Right now my only issues are on the Gorgias side of my Gorgias ← Pipedream–> Twitter integration I am building. So I think the actions I need are working fine.

There is a missing feature my dev team is looking at in that in the actions, “integrationid” which is required for Gorgias is not configurable, but I doubt that is something Pipedream needs to change.

user-1 · February 7, 2024, 10:01pm

Got it - let me know if there is something missing within our Gorgias components and I’d be happy to take a look.