Workforce management platform for scheduling and forecasting
Assembled currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New OOO Request
Triggers when a new OOO request is created.
OOO Status Changed
Triggers on approval/rejection of OOO.
Schedule Updated
Triggers when user schedule is modified.
Custom API Call
Make custom API calls to Assembled endpoints
Custom GraphQL
Perform a custom GraphQL query
Create OOO Request
Create an Out of Office request in Assembled.
Add Shift on Assembled
Add a new shift to a user's schedule in Assembled
Update OOO Request
Updates an existing OOO request.
Delete OOO Request
Cancel/delete a OOO request.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Assembled event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New OOO Request
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Assembled action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Custom API Call
Combine Assembled with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New OOO Request
Finishes with
Custom API Call, then preserve the outcome in Coherence
The exact authentication fields depend on Assembled. The workflow structure stays straightforward:
Authorize the Assembled account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Assembled or provide a complementary trigger or action.
Assembled currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Assembled currently lists 3 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Assembled triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
