What is the Slack Threads mock data preset useful for?
The Slack Threads preset generates channels and threaded messages with authors, avatars, edit state, reactions, resolution state, and timestamps for team chat and collaboration interfaces.
Generate API-ready mock data from this preset schema using the hosted mocking.dev faker API.
Edit, reorder, add, or remove fields before generating mock data from this preset.
This preview always requests one generated item from faker.mocking.dev, regardless of the download count.
The Slack Threads preset generates channels and threaded messages with authors, avatars, edit state, reactions, resolution state, and timestamps for team chat and collaboration interfaces.
The Slack Threads preset includes these top-level fields: id, channel, topic, messages, isResolved, createdAt. You can rename, remove, or extend the fields before generating data, including nested objects and arrays where supported.
Use it to test nested conversations, private channel badges, message ordering, edited labels, reaction counts, resolved threads, long discussions, and chat history pagination.
Customize the fields, row count, seed, and locale in the editor. The preview updates as you make changes, and you can download the generated records as a JSON file when the schema is ready.
Yes. mocking.dev uses Faker.js through its mock data API to generate names, emails, dates, numbers, locations, commerce data, and other realistic values. The seed makes results repeatable, while the locale controls regional data.
No. The records are synthetic and intended for development, demos, fixtures, and automated tests. Generated values can resemble real information by coincidence, so do not treat them as verified identities or use them to contact people.
{
id: string;
author: {
id: string;
displayName: string;
username: string;
avatarUrl: string;
isVerified: boolean;
};
content: string;
mediaUrls: string[];
likeCount: number;
commentCount: number;
repostCount: number;
isLikedByViewer: boolean;
hashtags: string[];
createdAt: string;
}{
id: string;
employeeNumber: string;
profile: {
fullName: string;
workEmail: string;
avatarUrl: string;
city: string;
country: string;
};
position: {
jobTitle: string;
department: string;
employmentType: string;
managerId: string;
};
compensation: {
annualSalary: string;
currency: string;
};
startedAt: string;
isActive: boolean;
}{
id: string;
key: string;
summary: string;
description: string;
status: string;
priority: number;
storyPoints: number;
reporter: {
id: string;
name: string;
avatarUrl: string;
};
assignee: {
id: string;
name: string;
avatarUrl: string;
};
labels: string[];
createdAt: string;
updatedAt: string;
}