Actions18
- Profiles Actions
- Posts Actions
- Media Actions
- Social Accounts Actions
- Connect Platform Actions
- Facebook Management Actions
- LinkedIn Management Actions
- Clone Connection Actions
Overview
The node provides functionality to clone an existing social media connection from one account or profile to another within the LATE platform. This is useful for users who manage multiple social media profiles or pages and want to replicate connection settings without manually reconfiguring each one. For example, a social media manager can clone a Facebook page connection from one account to another or duplicate LinkedIn organization connections efficiently.
Properties
| Name | Meaning |
|---|---|
| Profile ID | Target profile ID where the connection will be cloned. |
| Source Account ID | ID of the existing connection that you want to clone. |
| Target Page ID | Facebook page ID to target for cloning (specific to Facebook). |
| Target Page Name | Facebook page name for the target page (specific to Facebook). |
| Target Page Access Token | Facebook page access token for authentication on the target page (specific to Facebook). |
| Target Organization ID | LinkedIn organization ID to target (specific to LinkedIn). |
| Target Organization URN | LinkedIn organization URN for the target organization (specific to LinkedIn). |
| Target Organization Name | LinkedIn organization name for the target organization (specific to LinkedIn). |
| Target Account Type | LinkedIn account type to target; options are "Personal" or "Organization". |
Output
The node outputs JSON data representing the result of the clone operation. This typically includes details about the newly created or cloned connection such as its identifiers and status. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the LATE platform.
- The node communicates with the LATE API at
https://getlate.dev/api/v1. - Proper configuration of credentials in n8n is necessary to authorize requests.
Troubleshooting
- Missing Required Fields: Ensure that all required fields such as Profile ID and Source Account ID are provided; otherwise, the node will fail.
- Invalid Tokens or IDs: Incorrect Facebook page tokens or LinkedIn organization IDs/URNs may cause authentication or cloning errors.
- API Errors: If the LATE API returns errors, verify network connectivity and API key validity.
- Permission Issues: The user’s API key must have sufficient permissions to clone connections between accounts or organizations.
Links and References
- LATE Social Media Management Platform
- Refer to LATE API documentation for detailed information on cloning connections and required parameters.