Grant the roles/secretmanager.viewer and roles/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.
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, click Entities.
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, click Entities.
Select Profiles from the Entity 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 the Profiles 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# LinkedIn\n========\n\nThe LinkedIn connector lets you perform read operations on LinkedIn data.\n\nBefore you begin\n----------------\n\nIn your Google Cloud project, do the following tasks:\n\n- Ensure that network connectivity is set up. For information about network patterns, see [Network connectivity](/integration-connectors/docs/network-connectivity-private).\n- Grant the [roles/connectors.admin](/integration-connectors/docs/connectors-access-permissions#iam-roles-for-integration-connectors) IAM role to the user configuring the connector.\n- Grant the `roles/secretmanager.viewer` and `roles/secretmanager.secretAccessor` IAM roles to the [service account](/iam/docs/creating-managing-service-accounts#creating) that you want to use for the connector.\n- Enable the following services:\n - `secretmanager.googleapis.com` (Secret Manager API)\n - `connectors.googleapis.com` (Connectors API)\n\n To understand how to enable services, see [Enabling services](/service-usage/docs/enable-disable#enabling). If these services or permissions have not been enabled for your project previously, you are prompted to enable them when you configure the connector.\n\nConfigure the connector\n-----------------------\n\nA connection is specific to a data source. It\nmeans that if you have many data sources, you must create a separate connection\nfor each data source. To create a connection, do the following:\n\n1. In the [Cloud console](https://console.cloud.google.com), go to the **Integration Connectors \\\u003e Connections** page and then select or create a Google Cloud project.\n\n\n [Go to the Connections page](https://console.cloud.google.com/connectors/connections)\n2. Click **+ CREATE NEW** to open the **Create Connection** page.\n3. In the **Location** section, choose the location for the connection.\n 1. **Region** : Select a location from the drop-down list.\n\n For the list of all the supported regions, see [Locations](/integration-connectors/docs/locations).\n 2. Click **NEXT**.\n4. In the **Connection Details** section, complete the following:\n 1. **Connector** : Select **LinkedIn** from the drop down list of available Connectors.\n 2. **Connector version**: Select the Connector version from the drop down list of available versions.\n 3. In the **Connection Name** field, enter a name for the Connection instance.\n\n Connection names must meet the following criteria:\n - Connection names can use letters, numbers, or hyphens.\n - Letters must be lower-case.\n - Connection names must begin with a letter and end with a letter or number.\n - Connection names cannot exceed 49 characters.\n 4. Optionally, enter a **Description** for the connection instance.\n 5. Optionally, enable [Cloud logging](/integration-connectors/docs/view-connector-logs), and then select a log level. By default, the log level is set to `Error`.\n 6. **Service Account** : Select a service account that has the [required roles](#before-you-begin).\n 7. Optionally, configure the **Connection node settings** :\n\n\n - **Minimum number of nodes**: Enter the minimum number of connection nodes.\n - **Maximum number of nodes**: Enter the maximum number of connection nodes.\n\n A node is a unit (or replica) of a connection that processes transactions.\n More nodes are required to process more transactions for a connection and conversely,\n fewer nodes are required to process fewer transactions.\n To understand how the nodes affect your connector pricing, see\n [Pricing for connection nodes](/integration-connectors/docs/pricing#pricing-for-connection-nodes). If you don't enter any values, by default\n the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.\n | **Note:** You can customize the connection node values only if you are a Pay-as-you-go customer.\n 8. **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`.\n 9. Click **NEXT**.\n 10. In the **Authorization** section, enter details of the client ID and client secret.\n - **Client ID**: The client ID used for requesting access tokens.\n - **Scope**: A comma-separated list of desired scopes from the LinkedIn developer account.\n - **Client Secret**: Secret Manager Secret containing the client secret for the connected app you created.\n - **Secret version**: Secret version for the secret selected.\n 11. Click **NEXT**.\n 12. **Review**: Review your connection and authentication details.\n 13. Click **Create**.\n\n System limitations\n ------------------\n\n The LinkedIn connector can process a maximum of 5 transactions per second,\n per [node](/integration-connectors/docs/pricing#payg), and [throttles](/integration-connectors/docs/rate-limiting) any transactions beyond this limit LinkedIn enforces a limit of 10k requests per user every 24 hours.\n By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.\n\n For information on the limits applicable to Integration Connectors, see [Limits](/integration-connectors/docs/quotas).\n | **Note:** The number of [Integration Connectors nodes](/integration-connectors/docs/pricing#pricing-for-connection-nodes) will autoscale dynamically based on your usage. However, if you want to reserve capacity for large volumes without waiting for autoscaling, you can adjust the minimum node value for a connection. More nodes are required to process more transactions for a connection. Conversely, fewer nodes are required if a connection processes fewer transactions. To configure the node values, do the following:\n | - If you are a pay-as-you-go customer, configure the minimum and maximum node value in the edit connection page.\n | - If you are a subscription based customer, [contact support](/integration-connectors/docs/getting-support).\n |\n | The maximum transactions that a node can handle depends on various factors. So, before adjusting the minimum nodes for better throughput,\n | it is recommended you check if your backend systems are set up optimally to handle the required traffic.\n\n Use the LinkedIn connection in an integration\n ---------------------------------------------\n\n After you create the connection, it becomes available in both\n Apigee Integration and Application Integration. You can use the connection\n in an integration through the Connectors task.\n - To understand how to create and use the Connectors task in Apigee Integration, see [Connectors task](/apigee/docs/api-platform/integration/connectors-task#configure-the-connectors-task).\n - To understand how to create and use the Connectors task in Application Integration, see [Connectors task](/application-integration/docs/configure-connectors-task).\n\n Entities\n --------\n\n The LinkedIn connector supports entities, such as Comments and Profiles. To understand how to configure the\n entities, see [Entity examples](#entityexamples-exp).\n\n Entity operation examples\n -------------------------\n\n ### Example - List all the Comments from the LinkedIn profile page.\n\n This example lists all the Comments from the Posts in the Organization Pages that you administer\n 1. In the `Configure connector task` dialog, click `Entities`.\n 2. Select Comments from the `Entity` list.\n 3. Select the `LIST` operation, and then click **Done**.\n\n ### Example - Get Profiles from a specific ID\n\n This example gets the profiles based on the ID from the `Profiles` entity.\n 1. In the `Configure connector task` dialog, click `Entities`.\n 2. Select `Profiles` from the `Entity` list.\n 3. Select the `GET` operation, and then click **Done**.\n 4. In the **Task Input** section of the **Connectors** task, click **entityId** and then enter `2t7k5s4fgC` in the **Default Value** field.\n\n Here, `Id [KEY]` is the primary key value of the `Profiles` entity.\n 5. Click **Done**.\n\n Get help from the Google Cloud community\n ----------------------------------------\n\n You can post your questions and discuss this connector in the Google Cloud community at [Cloud Forums](https://www.googlecloudcommunity.com/gc/Integration-Services/bd-p/cloud-integration-services).\n\n What's next\n -----------\n\n - Understand how to [suspend and resume a connection](/integration-connectors/docs/suspend-resume-connection).\n - Understand how to [monitor connector usage](/integration-connectors/docs/cloud-monitoring).\n - Understand how to [view connector logs](/integration-connectors/docs/view-connector-logs)."]]