Can Greenhouse and Assembled talk in both directions?

Yes. Build one flow that starts in Greenhouse and acts in Assembled, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Greenhouse to Assembled

Move data between Greenhouse and Assembled the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Greenhouse Explore Assembled

Greenhouse triggers: 6
Greenhouse actions: 8
Assembled triggers: 3
Assembled actions: 6

Automation ideas

What you can build with Greenhouse and Assembled

A few flows teams run between Greenhouse and Assembled. Use one as a starting point, or build your own from scratch.

New Candidate Application in Greenhouse creates Custom API Call in Assembled
Triggers when a new application is submitted by a candidate.
New OOO Request in Assembled creates Create Candidate in Greenhouse
Triggers when a new OOO request is created.
New Candidate Application in Greenhouse creates Custom GraphQL in Assembled
Triggers when a new application is submitted by a candidate.
New OOO Request in Assembled creates Create Candidate Note in Greenhouse
Triggers when a new OOO request is created.
New Candidate Application in Greenhouse creates Create OOO Request in Assembled
Triggers when a new application is submitted by a candidate.
New OOO Request in Assembled creates Create Prospect in Greenhouse
Triggers when a new OOO request is created.