Perplexity Social Media Content — Turn Research into Scheduled Posts | Nimply

Name: Nimply
Author: Nimply

Most social content starts as research: what happened this week in your niche, what question your audience keeps asking, which angle nobody has covered yet. Perplexity is built for exactly that first half — it searches, reads, and synthesizes with sources attached. The second half, turning findings into posts on an actual schedule, has always meant leaving the app.

A Nimply connector removes that seam. Once connected, Perplexity's assistant can carry a research thread all the way through: gather the material, draft platform-shaped posts from it, and save them as drafts or scheduled posts in your Nimply workspace — bound for Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, or Threads. It can also look the other way, pulling your analytics to see what your audience actually engaged with before deciding what to research next.

What is Perplexity?

Perplexity is an AI answer engine: ask it a question and it searches the web, reads the results, and returns a synthesized, cited answer rather than a list of links. Its desktop apps and the Comet browser support connectors — MCP-based integrations that give the assistant tools beyond search, so it can act on services you use, not just report on the web.

Nimply is one such connector. The MCP server is hosted at https://mcp.nimply.io/mcp, so there is nothing to run yourself — you register the URL with an API key from your workspace's Settings → Developers page. That key is confined to one workspace and its permissions, and revoking it in Nimply disconnects Perplexity instantly.

What Perplexity can do with Nimply connected

Go from question to queued post in one thread

Ask Perplexity to research trending topics in your niche and draft three posts as Nimply drafts. The research, the writing, and the handoff to your content pipeline happen in a single conversation instead of three tools and a clipboard.

Start from what your audience already responded to

Perplexity can ask Nimply what your audience engaged with most last month, then use that as the brief for its next round of research. Content decisions get grounded in your own numbers rather than guesswork.

Keep a niche commentary series running

If part of your presence is reacting to industry news, the pairing is direct: Perplexity monitors and summarizes developments on request, drafts your take for each platform, and files everything into your Nimply queue for review.

Research broadly, publish carefully

Speed on the research side does not have to mean recklessness on the publishing side. Have Perplexity save everything as drafts, or push posts through Nimply's approval workflow so a person signs off before anything reaches an audience.

Connect Perplexity to Nimply

Perplexity supports MCP connectors in its desktop apps and the Comet browser. You need a Nimply workspace with a connected channel and an API key from Settings → Developers.

1
Create a Nimply API key
In Nimply, open Settings → Developers and create an API key. Keys start with nim_live_, belong to exactly one workspace, and can be revoked at any time.
2
Add a connector in Perplexity
Open Settings → Connectors in the Perplexity app and add a new connector. Choose the remote/HTTP server type — Nimply is a hosted server, so there is no command to configure.
3
Enter the server details
Point the connector at Nimply and authenticate with your key in the Authorization header:
Connector settings
```
URL:    https://mcp.nimply.io/mcp
Header: Authorization: Bearer nim_live_YOUR_KEY
```
4
Save and start a thread
Save the connector and the Nimply tools become available to the assistant. Try: "Research trending topics in my niche and draft three posts as Nimply drafts" or "What did my audience engage with most last month in Nimply?"

Frequently asked questions

Where in Perplexity does this work?

Connectors are supported in the Perplexity desktop apps and the Comet browser. If your version only supports local, command-based connectors, you can still connect through the mcp-remote bridge, using it as the command — see the generic MCP client guide in our developer docs.

Perplexity is not calling the Nimply tools — what should I check?

Connectors may need to be toggled on per thread; check the tools menu in the composer before assuming the setup failed. If you see a 401, recheck the header value — the whole string is Bearer nim_live_ followed by your key.

Which platforms can posts end up on?

Any channel connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. Perplexity creates real drafts and scheduled posts in the same queue you manage in the Nimply app.

Does Perplexity publish immediately, or can I review first?

You choose. Ask for drafts and everything waits in your workspace for review, or use Nimply's approval workflow so each post requires an explicit human approval. Direct scheduling is available when you want it, not the default you are stuck with.

What access does the connector actually have?

Exactly what the API key grants: one workspace, with the permissions you configured when creating the key in Settings → Developers. It cannot see other workspaces, and revoking the key severs the connection immediately.