Task Factory users running version 2020.1.4 or older (released prior to May 27, 2020): There's an important Task Factory update. Please visit here for more details.
Note: These Task Factory social media components require SQL Server version 2012 or higher.
Social OAuth Connection Manager
Important: To obtain Api Keys and Tokens, you need to first create an app developer account by visiting Facebook and Twitter's developer websites.
As of January 30, 2018, LinkedIn has been separated into its own connection manager due to their OAuth2 connection requirement. See the LinkedIn OAuth2 Connection Manager tab for more information.
The Social OAuth Connection Manager is used to set up a connection to social media sites. This connection manager is used within the Facebook Source and Twitter Source components.
Social OAuth Connection Settings
 |  |
| Option | Description |
|---|---|
| Service | Select this drop-down box to choose which social media to connect to. |
| (Twitter Options) Service Consumer Key (API Key) Consumer Secret (API Secret) Access Token Access Secret Token | Authentication information provided to users at Twitter's app developer site. |
| (Facebook Options) App ID App Secret Access Token | Authentication information provided to users at Facebook's app developer site. |
Social OAuth Advanced
 |  |
| Option | Description |
|---|---|
| Authentication Url | The Url (with version) of the social media site the user wants to connect to. |
| Proxy Host | The ip address of the proxy the user wishes to connect through. |
| Proxy Port | The port of the proxy being used. |
| Proxy User Name | Users should enter their user name for the proxy if it is required. |
| Proxy Password | Users should enter their password for the proxy if it is required. |
Facebook Source
| Source Icon | Source Description |
|---|---|
 | The Facebook Source is used to extract data such as your user profile, status updates, friends, likes, and comments within an SSIS package. See the Social OAuth Connection Manager to learn more about setting up this component's connection manager. |
Facebook Source Settings Tab
| Option | Description |
|---|---|
| Connection Manager | In this field, users can create a new connection manager or select a pre-existing one. |
| Api End Points | In this field, users select the endpoint they wish to connect to (such as User Profile or User Groups.) Selecting an endpoint auto-populates that field's parameters and commonly used Output Columns. |
| API Query | This field defines the query to be used in the API. Although several end points have been pre-configured, users can type in or paste custom calls that are not included with the component. These calls can be found by selecting the View Api Document link and adding the reference to the end of the API Query. Example: https://graph.facebook.com/{user-id}/groups |
| Root Json Path | Because Facebook returns the raw data in Json format, users need to define the root path when creating custom queries. |
| Query Parameters | User-defined parameters (such as id) based on the API query. Parameters can be set dynamically by entering the variable name. Example: <@User::ScreenName> |
| Output Columns | In this window, users can add and remove columns and define their name, token path (defined within the raw data), data type, length, precision, scale, and code page. |
Facebook Source Preview Tab
| Option | Description |
|---|---|
| Preview Data | Selecting this button returns the results and raw data based on the user-defined settings. |
| Results | In this window, users can see a preview of the first few rows of data based on their configuration. |
| Raw Data | This window displays the Json data in raw form. Developers can use this to help determine root and token paths. |
Twitter Source
| Source Icon | Source Description |
|---|---|
 | The Twitter Source is used to extract data such as status updates (known as Tweets), followers, hashtags, and retweeted or favorited tweets within an SSIS package. See the Social OAuth Connection Manager to learn more about setting up this component's connection manager. |
Twitter Source Settings Tab
| Option | Description |
|---|---|
| Connection Manager | In this field, users can create a new connection manager or select a pre-existing one configured earlier. |
| Api End Points | In this field, users select the Api they wish to connect to (such as User Timeline, Followers/List, etc.) Selecting an endpoint auto-populates that field's parameters and commonly used Output Columns. |
| API Query | This field defines the query to be used in the API. Although several end points have been pre-configured, users can type in or paste custom calls that are not included with the component. These calls can be found by selecting the View Api Document link, and copy & pasting the Resource URL located on the page of the selected API. |
| Root Json Path | Because Twitter returns the raw data in Json format, users need to define the root path when creating custom queries. This can (usually) be found in the View Api Document link under Example Result. |
| # Seconds to wait between API round trips | For security reasons, Twitter places a 200 count limit per call at runtime and only 15 calls can be performed within 15 minutes. This limitation can cause a too many requests error when querying a large dataset such as a user's followers which has 10,000 users. To avoid this error, users can set a timer that pauses between calls. |
| Query Parameters | User-defined parameters (such as screenname or count number.) Parameters can be set dynamically by entering the variable name. Example: <@User::ScreenName> |
| Output Columns | In this window, users can add and remove columns and define their name, token path (defined within the raw data), data type, length, precision, scale, and code page. |
Twitter Source Preview Tab
| Option | Description |
|---|---|
| Preview Data | Selecting this button returns the results and raw data based on the user-defined settings. |
| Results | In this window, users can see a preview of the first few rows of data based on their configuration. |
| Raw Data | This window displays the Json data in raw form. Developers can use this to help determine a root and token path. |
LinkedIn OAuth2 Connection Manager
Unsupported: The LinkedIn component was deprecated in version 2019.4.1 and is no longer supported.
The LinkedIn OAuth2 Connection manager is used with the LinkedIn Source data flow component.
Additional Information: Before using the LinkedIn Source, users must first create an app to obtain a Client ID and Client Secret. This can be done by visiting LinkedIn Developers.
LinkedIn OAuth2 Connection Settings
| Option | Description |
|---|---|
| Client Id | Enter the Client ID provided by LinkedIn. |
| Client Secret | Enter the Client Secret provided by LinkedIn. Note: Client ID and Client Secret are located in the My Apps - Authentication Keys section at LinkedIn Developers. |
| Access Token | LinkedIn's OAuth2 connection requires an access token to make API requests. Select the Get Token button to open the Token Getter window. |
| Is Bearer Token | LinkedIn requires access tokens be designated as bearer tokens. This option is automatically selected after the user has created an access token in the previous step. |
| Access Token Expiration Date | Identifies the date and time a user's access token expires. This field automatically populates when the user completes the steps in the Get Token window. |
| Test Connection | Tests the connection after the connection manager has been configured. |
OAuth2 Get Token
The Token Getter window displays when users select the Get Access Token button.
| Option | Description |
|---|---|
| Client ID | The client ID entered in the connection settings. |
| Client Secret | The client secret entered in the connection settings. |
| Authorized Redirect Url | This is a required field. It must match a redirect URL configured within LinkedIn's developer website (located in the My Apps - OAuth 2.0 section). |
| Scopes | Identifies the default application permissions. Users can add the following scopes:
|
| State | A unique string value similar to a password. The state can be any word, number, or character combination that does not contain a space. |
| Get Access Token | After all fields have been completed, select the Get Access Token button to receive it. This opens a small browser within the window. The user must authenticate to LinkedIn and allow access to the API to complete the process. |
LinkedIn OAuth2 Headers
| Option | Description |
|---|---|
| Headers | LinkedIn requires a connection header called x-li-format with the value Json. This is automatically entered after the user completes the steps in the Get Token window. |
| Add New Header | Creates a new header. |
| Remove Header | Removes a selected header. |
LinkedIn OAuth2 Proxy
| Option | Description |
|---|---|
| Proxy Host | Identifies the proxy address. |
| Proxy Port | Identifies the port used by the proxy. |
| Proxy User Name | Enter the user name for proxies that require user authentication. |
| Proxy Password | Enter the password for proxies that require user authentication. |
| Auth Scheme | Identifies which authentication scheme the proxy is using. |
LinkedIn Source
Unsupported: The LinkedIn component was deprecated in version 2019.4.1 and is no longer supported.
| Source Icon | Source Description |
|---|---|
 | The LinkedIn Source is used to extract data such as name, status updates, connections, and headlines within an SSIS package. See the LinkedIn Social OAuth2 Connection Manager to learn more about setting up this component's connection manager. |
| Option | Description |
|---|---|
| Connection Manager | In this field, users can create a new connection manager or select a pre-existing one. |
| Api End Points | In this field, users select the Api they wish to connect to (Get My Profile and Get Member Profile.) Selecting an endpoint auto-populates that field's parameters and commonly used Output Columns. |
| API Query | This field defines the query to be used in the API. Although several end points have been pre-configured, users can type in or paste custom calls that are not included with the component. Note: Unfortunately, LinkedIn does not provide a comprehensive list of API calls so users have to search the internet if they wish to customize this field. |
| Root Json Path | Because LinkedIn returns the raw data in Json format, users need to define the root path when creating custom queries. |
| Query Parameters | User-defined parameters (such as id) based on the API query. Parameters can be set dynamically by entering the variable name. Example: <@User::ScreenName> |
| Output Columns | In this window, users can add and remove columns and define their name, token path (defined within the raw data), data type, length, precision, scale, and code page. |
LinkedIn Source Preview
| Option | Description |
|---|---|
| Preview Data | Selecting this button returns the results and raw data based on the user-defined settings. |
| Results | In this window, users can see a preview of the first few rows of data based on their configuration. |
| Raw Data | This window displays the Json data in raw form. Developers can use this to help determine a root and token path. |
