fetch_twitter
Enriches a dataset containing tweets with information about their authors.
In addition to author information also adds the location the tweet was send from (if available), and indicates whether a tweet was retweeted or favourited at least once. See below for a detailed list of the enrichment columns.
???+ info “API integration” To use this step you will need to create an app associated to your Twitter account, and obtain four items: the consumer_key, the consumer_secret, the token and the token_secret.
To do so you can follow the steps here, and then add them to a Graphext integration.
Usage
The following example shows how the step can be used in a recipe.
Examples
Examples
This step doesn’t have any configuration parameters. Hence simply:
This step doesn’t have any configuration parameters. Hence simply:
General syntax for using the step in a recipe. Shows the inputs and outputs the step is expected to receive and will produce respectively. For futher details see sections below.
Inputs & Outputs
The following are the inputs expected by the step and the outputs it produces. These are generally
columns (ds.first_name
), datasets (ds
or ds[["first_name", "last_name"]]
) or models (referenced
by name e.g. "churn-clf"
).
Inputs
Inputs
Twitter’s unique identifier for each tweet.
Outputs
Outputs
Time the user who tweeted this tweet was created.
Self-description of the user.
How many tweets the user has favorited.
How many followers the user has.
How many users the user is following.
How many times the user has been listed in public listings.
User’s picture.
Whether this user has protected their tweets or not.
How many times this user has tweeted.
User’s profile url.
Whether this user is verified or not.
Location extracted from the author profile.
Latitude this tweet was tweeted from.
Longitude this tweet was tweeted from.
Whether you have retweeted this tweet.
Whether you have favorited this tweet.
Where this tweet was tweeted from as a HTML string.
Configuration
The following parameters can be used to configure the behaviour of the step by including them in
a json object as the last “input” to the step, i.e. step(..., {"param": "value", ...}) -> (output)
.
Parameters
Parameters
ID of the integration you’d like to use.