The LinkedIn connector lets you perform read operations on LinkedIn data.
Before you begin
In your Google Cloud project, do the following tasks:
- Ensure that network connectivity is set up. For information about network patterns, see Network connectivity.
- Grant the roles/connectors.admin IAM role to the user configuring the connector.
- Grant the
roles/secretmanager.viewer
androles/secretmanager.secretAccessor
IAM roles to the service account that you want to use for the connector. - Enable the following services:
secretmanager.googleapis.com
(Secret Manager API)connectors.googleapis.com
(Connectors API)
To understand how to enable services, see Enabling services. If these services or permissions have not been enabled for your project previously, you are prompted to enable them when you configure the connector.
Configure the connector
A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following:
- In the Cloud console, go to the Integration Connectors > Connections page and then select or create a Google Cloud project.
- Click + CREATE NEW to open the Create Connection page.
- In the Location section, choose the location for the connection.
- Region: Select a location from the drop-down list.
For the list of all the supported regions, see Locations.
- Click NEXT.
- Region: Select a location from the drop-down list.
- In the Connection Details section, complete the following:
- Connector: Select LinkedIn from the drop down list of available Connectors.
- Connector version: Select the Connector version from the drop down list of available versions.
- In the Connection Name field, enter a name for the Connection instance.
Connection names must meet the following criteria:
- Connection names can use letters, numbers, or hyphens.
- Letters must be lower-case.
- Connection names must begin with a letter and end with a letter or number.
- Connection names cannot exceed 49 characters.
- Optionally, enter a Description for the connection instance.
- Optionally, enable Cloud logging,
and then select a log level. By default, the log level is set to
Error
. - Service Account: Select a service account that has the required roles.
- Optionally, configure the Connection node settings:
- Minimum number of nodes: Enter the minimum number of connection nodes.
- Maximum number of nodes: Enter the maximum number of connection nodes.
A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
- Company Id: The LinkedIn company ID that is unique to your organization. If you specify the Company ID in the query, use the following format:
urn:li:organization:COMPANY_ID
. - Click NEXT.
- In the Authorization section, enter details of the client ID and client secret.
- Client ID: The client ID used for requesting access tokens.
- Scope: A comma-separated list of desired scopes from the LinkedIn developer account.
- Client Secret: Secret Manager Secret containing the client secret for the connected app you created.
- Secret version: Secret version for the secret selected.
- Click NEXT.
- Review: Review your connection and authentication details.
- Click Create.
System limitations
The LinkedIn connector can process a maximum of 5 transactions per second, per node, and throttles any transactions beyond this limit LinkedIn enforces a limit of 10k requests per user every 24 hours.
By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.For information on the limits applicable to Integration Connectors, see Limits.
Use the LinkedIn connection in an integration
After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.
- To understand how to create and use the Connectors task in Apigee Integration, see Connectors task.
- To understand how to create and use the Connectors task in Application Integration, see Connectors task.
Entities
The LinkedIn connector supports entities, such as Comments and Profiles. To understand how to configure the entities, see Entity examples.
Entity operation examples
Example - List all the Comments from the LinkedIn profile page.
This example lists all the Comments from the Posts in the Organization Pages that you administer
- In the
Configure connector task
dialog, clickEntities
. - Select Comments from the
Entity
list. - Select the
LIST
operation, and then click Done.
Example - Get Profiles from a specific ID
This example gets the profiles based on the ID from the
Profiles
entity.- In the
Configure connector task
dialog, clickEntities
. - Select
Profiles
from theEntity
list. - Select the
GET
operation, and then click Done. - In the Task Input section of the Connectors task, click entityId and
then enter
2t7k5s4fgC
in the Default Value field.Here,
Id [KEY]
is the primary key value of theProfiles
entity. - Click Done.
Get help from the Google Cloud community
You can post your questions and discuss this connector in the Google Cloud community at Cloud Forums.What's next
- Understand how to suspend and resume a connection.
- Understand how to monitor connector usage.
- Understand how to view connector logs.