Work in Acme rarely ends in Acme. A plan goes into a calendar, a finished draft into an email, a status into a team channel. Integrations take results out of the workspace without copying them by hand.
What is available
Connect them
Slack notifications
Pick a channel once.
Open Workspace → Integrations → Slack, choose a channel and the events you want: a shared workflow finished, a comment on a draft. Change or remove it at any time.
Calendar export
A live link for any calendar app.
Open a plan and choose Export → Calendar link. Paste the link into your calendar app. Changes in Acme show up there within a few minutes.
Copy and export
Formatting survives.
Every answer has a copy button, and lists and tables keep their formatting when pasted into a document or an email. A result can also be exported as a document.
From your code
Every request needs a personal token.
Issue a token in your profile and send it as a bearer header. Tokens act as you, so keep them out of shared files.
API in one call
List the projects you can see:
curl -s -H "Authorization: Bearer $ACME_TOKEN" \
"https://api.example.com/v1/projects?limit=10"The answer is a list of projects with their ids, names and counts:
{
"items": [
{ "id": "prj_42", "name": "Monthly update", "workflows": 3 }
]
}Anyone holding your token can do what you can do. If it leaks, delete it in your profile and issue a new one.
Put it together
Plan to calendar in three steps
Build the workflow
Make a Monday plan workflow and schedule it to prepare drafts.
Export the plan
Copy the calendar link from the plan.
Add Slack
Choose the channel where the team wants to hear about shared workflows.
Frequently asked questions
Can Acme publish for me?
No. Acme prepares results and notifies you; sending and publishing stay a decision you make.
Which plans include the API?
The API is available on paid plans with a personal token. Check Pricing for current limits.
Where do I see what was sent to Slack?
In the Slack channel itself. Acme sends only what you selected when you connected it.