> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/social-posts-data/employee-posts.md).

# Employee Posts Data

Employee Posts Data provides freshly collected professional network posts with engagement metrics, authorship details, and publication timestamps.

Employee Posts Data is designed to be used in **Sales Tech, Investment, Market Research, and AI/ML applications.**

| **Enhanced sales personalization** | Access to full post content enables highly personalized outreach based on prospects' actual interests, achievements, and current priorities.                            |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Company intelligence**           | Capture unique business insights and news directly from employee posts that may not appear in traditional news sources.                                                 |
| **Intent signal detection**        | Identify optimal timing for outreach based on company funding announcements, executive changes, product launches, and other business developments shared through posts. |

***

## Summary

| Feature            | Details        |
| ------------------ | -------------- |
| Available via      | Flat files/API |
| Delivery frequency | Monthly        |
| Available formats  | JSONL, Parquet |
| Scraping since     | 2025-03        |

## Related links

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><a href="/social-posts-data/employee-posts/data-dictionary.md">Dictionary: Employee Posts Data</a></td></tr><tr><td><a href="/social-posts-data/employee-posts/record-sample.md">Sample: Employee Posts Data</a></td></tr><tr><td><a href="/social-posts-data/employee-posts-api.md">Employee Posts API</a></td></tr></tbody></table>

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/social-posts-data/employee-posts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.