Install the Skylane app in Make

Step-by-step guide
  • About 15 minutes
  • 9 steps
  • Growth and Agency
  • Checked 2 Nov 2026
0 of 9 steps done

The Skylane app is not in Make's public app list yet: a public listing needs Make's review, which is pending. Until then you install it as a private app in your own Make organisation, as below.

Before you start

  • A Make account where you can create custom apps (Custom apps in the left-hand menu of Make).
  • A Skylane API key with accounts:read, posts:read, posts:write, media:write and webhooks:write - see Create and use an API key.
  • The app definition files from Skylane's integrations/make folder. Ask Skylane support for a copy if you do not have them.

Steps

  1. Step 1

    Create the app in Make

    In Make, click Custom apps, then Create a new app. Set Name to skylane, Label to Skylane and Description to Schedule social posts with Skylane, then click Save.

  2. Step 2

    Paste the base

    Open the Base tab, replace everything with the contents of base.json and click Save. It points every call at the Skylane API and sends your key as a Bearer token.

  3. Step 3

    Add the connection

    Open Connections, click Create a new connection, set Label to Skylane API key and Type to API key, then paste connections/api-key/parameters.json into Parameters and connections/api-key/api.json into Communication. Save both tabs.

  4. Step 4

    Add the webhook

    Open Webhooks, click Create a new webhook, set Label to Skylane events, Type to Dedicated and Connection to Skylane API key. Paste each file from webhooks/post-events/ into the tab with the same name (Communication, Parameters, Attach, Detach) and save.

  5. Step 5

    Add the account picker

    Open Remote procedures, click Create a new RPC, set Name to listAccounts and Connection to Skylane API key, paste rpcs/listAccounts/api.json into Communication and save.

  6. Step 6

    Add the modules

    Open Modules and create each one with the name, label, description and type in its module.json: createPost (Action), schedulePost (Action), listAccounts (Search), uploadMediaFromUrl (Action) and watchPostEvents (Instant trigger, using the Skylane events webhook). Set Connection to Skylane API key, then paste api.json into Communication, expect.json into Mappable parameters and interface.json into Interface, and save.

  7. Step 7

    Connect your key

    In a scenario, add Skylane, then List accounts. Click Add next to Connection, paste your API key into API key and click Save. Make checks the key by calling /api/v1/me.

  8. Step 8

    Build a scenario

    For example: RSS - Watch RSS feed items, then Skylane - Create and schedule a post with Caption mapped to the item title and link, Accounts chosen from the list, When set to Add to queue and Idempotency key mapped to the item's ID. Run it once to test.

  9. Step 9

    React to post events

    Start a scenario with Skylane - Watch post events and choose the events. Make registers a Developer webhook in your Skylane account for you (it appears under Settings, then Developer) and removes it when you delete the trigger.

Good to know

  • Everything a scenario does goes through the same pre-flight checks, plan limits and approvals as the app. Problems come back as errors with the reason and a fix.
  • Make counts towards the key's requests-a-minute limit. Add a Sleep module if a scenario loops over many items.
  • To share the app with a teammate's Make organisation, open the app in Make and use Invite under its options. It stays private to the people you invite.

Common problems

"Invalid or missing API key"

Paste the full key, starting skyl_, with no spaces. Check it is not revoked.

Watch post events never fires

Check Settings, then Developer: the webhook Make created should be Active. If it was paused after failures, click Resume.

"This API key does not have the ... permission"

Create a key with the permission named in the message and update the connection.

Official documentation

Still stuck? Contact support

Tell us which step you reached and what you see on screen. A screenshot helps.