Twitter Integration

The Pathfix Twitter Connector plugin enables integration from your Bubble app to your user's Twitter. The plugin will render the Connect button (UI) and calls the relevant Twitter API automatically. No configurations required to get the plugin working

This documentation will show setup guide and a few example use cases.


The plugin is available in the Bubble Plugin store.

(Important Note: You need to install the Pathfix OAuth Connector first before installing this plugin)

  • Log into your Bubble app and click on Add Plugin
  • Pick the Twitter (OAuth) plugin by Pathfix Inc. and install it (click here to access the plugin)

  • Under x-partner-key (shared headers), add your Pathfix x-partner-key from the Keys section of your Pathfix account
  • If you do not have a Pathfix account, enter the x-partner-key provided by the Pathfix OAuth Connector plugin in preview mode


The x-partner-key generated by the Pathfix OAuth plugin are intended for testing and not production environments. Login to your account and add the provider to use your own keys in Pathfix.

Image: plugin page
Image: plugin page

  • Navigate to the Design section and select the Pathfix Connector element and enable Twitter from the list of providers

Image: enable provider
Image: enable provider

Once installed, there are no additional configurations required to get the Plugin to work. You can setup your workflow in Bubble and start using the actions.

The Connect button will automatically be added to your page that contains the Pathfix Connector Design Element. No additional settings are required

You can add Dropdown, text etc elements to pull in Twitter data for your users using the plugin and setup Workflows to Twitter actions.

Actions Available

The Connector plugin calls a few APIs and offers them as Actions in your Bubble Workflow once installed. These are:

Image: Twitter actions
Image: Twitter actions

Note: Each consumed action is counted as 1 API call in Pathfix


The plugin works with a Pathfix ClientID and ClientSecret. This means that when your user goes through the OAuth process to grant access, they will see the request by Pathfix. This is intended for testing functionality and not for production environments.

You can use your own ClientID and ClientSecret in the plugin and whitelabel it.

Follow this document to Whitelabel Your Connectors

Works with