You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/connect-data/reference/linkedin.md
+45-24Lines changed: 45 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,7 @@ The following section is a reference guide that provides a complete description
28
28
29
29
<dd>
30
30
31
-
You can authenticate using OAuth 2.0. To connect LinkedIn to Appsmith, you'll need to:
32
-
33
-
1.**Set up a LinkedIn Developer App**:
34
-
- Navigate to the [LinkedIn Developer Portal](https://www.linkedin.com/developers/).
35
-
- Create a new application to obtain your **Client ID** and **Client Secret**.
36
-
- Configure the necessary OAuth 2.0 redirect URLs and permissions (scopes) required for your application.
37
-
38
-
2.**Configure the LinkedIn Integration**:
39
-
- In Appsmith, when creating a new LinkedIn datasource, you'll be prompted to authenticate.
40
-
- Review the requested permissions and click **Allow** to grant Appsmith access to your LinkedIn account.
41
-
- The OAuth flow provides secure access to your LinkedIn profile and content based on the permissions granted.
31
+
LinkedIn uses OAuth 2.0. When you create a LinkedIn datasource in Appsmith, the OAuth client configuration is handled for you—simply click **Authorize**, review the requested permissions, and approve the connection. The OAuth flow will open LinkedIn in a browser tab where you can grant Appsmith access to your LinkedIn account.
42
32
43
33
The authentication process requires you to have a browser session and will redirect you to LinkedIn's authorization page where you can approve the connection.
44
34
@@ -198,10 +188,9 @@ Check out our latest product launch!
198
188
199
189
The media category specifies the type of media being shared in the post. This field is mandatory and accepts the following values:
200
190
201
-
-**`IMAGE`** - For image media
202
-
-**`VIDEO`** - For video media
203
-
-**`ARTICLE`** - For article media
204
-
-**`NONE`** - For posts without media
191
+
-**`IMAGE`** - For image
192
+
-**`VIDEO`** - For video
193
+
-**`ARTICLE`** - For article
205
194
206
195
*Example:* To specify an image post:
207
196
@@ -226,7 +215,7 @@ The structure should follow LinkedIn's UGC (User Generated Content) API format:
**Note:** The `media` field should contain a URN from a previously registered asset upload. You'll need to use LinkedIn's asset upload API to register media before creating the post.
241
+
**Note:** The `media` field should contain a URN from a previously registered asset upload. Use the [Register Media Upload Request](#register-media-upload-request) action to create the asset before posting.
After you receive the `uploadUrl`, upload the binary file contents directly to LinkedIn using a REST API **PUT** request:
326
+
327
+
1. Add a **FilePicker** widget and set its **Data Format** to **Binary**.
328
+
2. Create a new REST API action and set **Method** to `PUT`.
329
+
3. Set the **URL** to `{{RegisterMediaUploadRequest.data.value.uploadMechanism["com.linkedin.digitalmedia.uploading.MediaUploadHttpRequest"].uploadUrl}}`.
330
+
4. Add headers:
331
+
-`Content-Type: {{FilePicker1.files[0].type}}`
332
+
5. Set the **Body** to **Binary** and provide `{{FilePicker1.files[0].data}}` as the value.
333
+
6. Run the API to upload the image/video bytes, which completes the media upload for the returned `media` URN.
334
+
314
335
### Get Media Upload Status
315
336
316
337
The Get Media Upload Status command checks the upload/processing status of media (image, video, or document) on LinkedIn using the LinkedIn API via a proxy. This is useful for monitoring the status of uploaded media assets before using them in posts or other LinkedIn content.
@@ -321,9 +342,9 @@ The Get Media Upload Status command checks the upload/processing status of media
321
342
322
343
The type of media to check status for. This field is mandatory and accepts three values:
323
344
324
-
-**`image`** - For image media
325
-
-**`video`** - For video media
326
-
-**`document`** - For document media
345
+
-**`image`** - For image
346
+
-**`video`** - For video
347
+
-**`document`** - For document
327
348
328
349
*Example:* To check status of an image:
329
350
@@ -342,7 +363,7 @@ The unique identifier of the media to check status for. This is the media ID ret
342
363
*Example:* If you want to dynamically check status using a media ID from a previous query:
0 commit comments