LATE
Actions18
- Profiles Actions
- Posts Actions
- Media Actions
- Social Accounts Actions
- Connect Platform Actions
- Facebook Management Actions
- LinkedIn Management Actions
- Clone Connection Actions
Overview
This node operation, Clone Connection, is designed to duplicate an existing social media connection profile within the LATE platform. It allows users to clone a connection from a source account to a target profile, optionally specifying details for Facebook or LinkedIn targets. This is useful when managing multiple social media accounts or pages and wanting to replicate settings or connections without manually reconfiguring each one.
Common scenarios:
- Cloning a Facebook page connection to another Facebook page under a different profile.
- Duplicating a LinkedIn organization connection to a new LinkedIn organization or personal account.
- Quickly setting up similar social media connections across multiple profiles or accounts in LATE.
Practical example:
A social media manager wants to clone an existing Facebook page connection from one clientās account to another clientās profile, including access tokens and page details, to streamline post scheduling and management.
Properties
| Name | Meaning |
|---|---|
| Profile ID | Target profile ID where the cloned connection will be created. |
| Source Account ID | ID of the existing connection that will be cloned. |
| Target Page ID | Facebook page ID to target (used only for Facebook connections). |
| Target Page Name | Facebook page name (used only for Facebook connections). |
| Target Page Access Token | Facebook page access token (used only for Facebook connections). |
| Target Organization ID | LinkedIn organization ID (used only for LinkedIn connections). |
| Target Organization URN | LinkedIn organization URN (used only for LinkedIn connections). |
| Target Organization Name | LinkedIn organization name (used only for LinkedIn connections). |
| Target Account Type | LinkedIn account type; options are Personal or Organization (used only for LinkedIn connections). |
Output
The node outputs JSON data representing the result of the cloning operation. This typically includes confirmation of the cloned connection details such as new connection IDs, status messages, or any relevant metadata returned by the LATE API.
If binary data were involved (e.g., media files), it would be summarized here, but this operation focuses on connection metadata only.
Dependencies
- Requires an API key credential for authenticating with the LATE platform API.
- The node communicates with the LATE API endpoint at
https://getlate.dev/api/v1. - Proper permissions on the source account and target profile are necessary to perform cloning.
- For Facebook cloning, valid page access tokens are required.
- For LinkedIn cloning, valid organization IDs, URNs, and account types must be provided.
Troubleshooting
- Missing or invalid credentials: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid source account ID: Verify that the source account ID exists and is accessible.
- Incorrect target identifiers: For Facebook or LinkedIn, ensure that the target page or organization IDs, names, and tokens are accurate and valid.
- API errors: The LATE API may return errors if cloning limits are exceeded or if the target profile does not support the requested connection type.
- Permission issues: The user must have appropriate rights on both source and target profiles/accounts to perform cloning.
Links and References
- LATE Platform Documentation (for API usage and authentication)
- Facebook Developer Documentation (for page access tokens and page IDs)
- LinkedIn Developer Documentation (for organization URNs and account types)