zedgad

Publish once. Share everywhere.

zedgad helps you turn one project into a posting hub. Write updates manually, or connect your website so new jobs, news, products, events, and announcements can flow into your social channels automatically.

Create your first projectSign in

Project hub

CareJobs Canada

Content received from website
Post prepared for Facebook Page
Post prepared for LinkedIn Page
Publish logs saved for review

Webhook

POST /api/webhooks/content/Authorization: Bearer zg_live_xxxxx

The usual mess

Your content goes live in one place. Your audience lives everywhere else.

A recruiter posts a new job on their website. A shop adds a new product. A news team publishes a story. An event organizer announces a new show. The source is different, but the next step is usually the same: copy, paste, rewrite, and repost across social media.

That manual work is easy to forget, hard to track, and painful to repeat. zedgad exists for that moment after publishing, when the update needs to leave your website or dashboard and reach the places people actually check.

Path one

Start manually, even before you connect a website.

Some users just want a calmer way to post across their social media handles. That should not require a webhook, a developer, or a complicated setup. Create a project, connect your accounts, and publish from zedgad.

Write once

Create a post inside your project with a title, summary, link, and optional details.

Choose channels

Select the connected social pages or handles that should receive the update.

Publish

Send the update from one place instead of rebuilding it for each platform.

Review logs

See what posted, what failed, and what needs attention.

Path two

When your website publishes, zedgad can take it from there.

For job boards, blogs, shops, listing sites, and internal tools, zedgad becomes the receiving point. Your system sends structured content through an API key, and the project keeps the incoming content, social accounts, and publish history together.

Website

Webhook

Social pages

01A new job, article, product, event, or announcement is published.
02Your website sends the content to the zedgad webhook.
03zedgad saves it under the right project.
04The content is prepared for the connected social channels.
05Publish logs show every success and failure.
Example payload
{
  "type": "job",
  "title": "Care Assistant",
  "url": "https://example.com/jobs/care-assistant"
}

The project model

Everything lives inside a project.

That keeps the product simple. A project owns the social accounts, API keys, received content, and publishing history for one brand or workflow.

Project

A project can represent a brand, client, website, business, or personal posting presence.

API keys

Each project can have its own keys, so incoming content is tied to the right hub.

Social accounts

Connected pages and handles belong to the project that will publish through them.

Content inbox

Manual posts and webhook content land in one place before or after publishing.

Publish logs

Every attempt leaves a trail, so you can see what happened without guessing.

Not just jobs

If it can be published, it can be shared.

Job boards are a strong first use case, but zedgad should not be boxed into one industry. The same project flow works for any repeatable content that needs to move from a source into social channels.

News storiesJob postsProductsEventsReal estate listingsAnnouncementsBlog postsCustom updates

Start light

Create a project first. Automate when you are ready.

You can begin with manual posting, then add API keys and webhook automation when your website or backend is ready to send content into zedgad.

Create your first project