What are the Implications of Twitter API Paid Plans on Workflows?

1

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

How will Twitter API work with workflows when they move to paid plans on February 9th?

2

Hi Soyab, I recommend switching to using your own Twitter Developer App for your Twitter integrations:

Then you’ll be able to use your own Twitter app and plan separate from the Pipedream Twitter app.

3

wait what?

4

well crap: Twitter will charge developers to access its API starting February 9th | Engadget

5

Yes, very short notice unfortunately

6

if i have a workflow i forget to disable, will i be charged? or will it break (im fine with it just breaking)

7

I do not imagine that we will not be charging downstream for the official Pipedream Twitter app usage.

If they include a base number of free API actions, we’d pass it downstream to implementors. But I don’t believe that we would provide a paid plan.

We’ll have more information later once our team is all online and can discuss.

What I believe is most likely at this point is that we disable our Twitter app integration if they require a paid subscription for any usage.

8

k. i think ive killed all of mine off successfully

9

> I recommend switching to using your own Twitter Developer App for your Twitter integrations

  • would this just involve provisioning our own Twitter API keys that we can supply in our Pipedream workflows such that the charges of the API calls are directly billed to us outside of Pipedream?
10

Hi exactly. You would then be able to set up billing directly with Twitter and use Pipedream as the integration platform.