Skip to main content

Run a Temporal Application in PHP

Temporal PHP SDK


This tutorial is a work in progress. Some sections may be incomplete, out of date, or missing. We're working to update it.

In this tutorial, you'll explore the different components that make up a Temporal project using the PHP SDK, including:

  • Temporal Client
  • Workflow and Activity Code
  • Temporal Worker (running with RoadRunner)

All the code on this page is included in the SimpleActivity sample, from our Samples repository.

Downloading the project

Clone the project repository and navigate to the project directory:

git clone
cd samples-php

Start the Temporal Server and application containers:

docker-compose up

This starts Temporal Server with the docker-compose.yml that ships with the samples-php repository. When it's live, you can access Temporal Web at http://localhost:8080 although you won't see any Workflows run yet.

Run the application

The program you'll run is a console command that starts a workflow, prints its IDs, and then waits for its result.

Execute the following command to run the program:

docker-compose exec app php app.php simple-activity

This prints the Workflow ID (and corresponding Run ID) that is started, and you'll see it reflected in the Temporal Web UI.

At the end it will log the result:

Starting GreetingWorkflow...
Started: WorkflowID=3520711c-7c8b-4d36-bd18-68328e60447b
Hello Antony

Let's explore each piece of the code and how it works with Temporal.

The Workflow Client

In the following snippet, WorkflowClientInterface is the entry point to get access to workflows. When you need to create, retrieve, or start a workflow you'll use an instance of WorkflowClientInterface.

Here we create an instance of GreetingWorkflowInterface with execution timeout of 1 minute. Then we print some information and start the workflow.


class ExecuteCommand extends Command
protected const NAME = 'simple-activity';
protected const DESCRIPTION = 'Execute SimpleActivity\GreetingWorkflow';

public function execute(InputInterface $input, OutputInterface $output): int
$workflow = $this->workflowClient->newWorkflowStub(

$output->writeln("Starting <comment>GreetingWorkflow</comment>... ");

// Start a workflow execution. Usually this is done from another program.
// Uses task queue from the GreetingWorkflow @WorkflowMethod annotation.
$run = $this->workflowClient->start($workflow, 'Antony');

'Started: WorkflowID=<fg=magenta>%s</fg=magenta>',

// getResult waits for workflow to complete
$output->writeln(sprintf("Result:\n<info>%s</info>", $run->getResult()));

return self::SUCCESS;

Now let's look at the workflow.

Workflow interface and implementation

With the PHP SDK, you define an interface and an implementation.

First, let's take a look at the workflow interface:


use Temporal\Workflow\WorkflowInterface;
use Temporal\Workflow\WorkflowMethod;

interface GreetingWorkflowInterface
* @param string $name
* @return string
#[WorkflowMethod(name: "SimpleActivity.greet")]
public function greet(
string $name

The important thing here are attributes #[WorkflowInterface] and #[WorkflowMethod]. Both of them define the "workflow". The first one marks the class/interface, the second one marks the method in the class/interface.

In our case the workflow is the method that accepts string $name. To see what it actually does, look at the implementation in the class GreetingWorkflow:


class GreetingWorkflow implements GreetingWorkflowInterface
private $greetingActivity;

public function __construct()
* Activity stub implements activity interface and proxies calls to it to Temporal activity
* invocations. Because activities are reentrant, only a single stub can be used for multiple
* activity invocations.
$this->greetingActivity = Workflow::newActivityStub(

public function greet(string $name): \Generator
// This is a blocking call that returns only after the activity has completed.
return yield $this->greetingActivity->composeGreeting('Hello', $name);

This is the implementation of our workflow. It communicates with one activity and delegates all the work to it.

In the constructor we create an instance of the GreetingActivityInterface with maximum execution time of 2 seconds.

In method greet() we call our activity.

Here the workflow pauses and waits until the activity is done and only then returns the result.

It is achieved with a call to yield.

To instantiate an instance of the activity we use a static helper Workflow::newActivityStub().

Activity interface and implementation

And at last we arrive at the activity code. Consider it as a particular task in the business logic. As you have noticed we again use an interface to instantiate an object:


use Temporal\Activity\ActivityInterface;
use Temporal\Activity\ActivityMethod;

#[ActivityInterface(prefix: 'SimpleActivity.')]
interface GreetingActivityInterface
#[ActivityMethod(name: "ComposeGreeting")]
public function composeGreeting(
string $greeting,
string $name
): string;

Activities and workflow classes in PHP are marked with special attributes. For activity, we use #[ActivityInterface] and #[ActivityMethod]. The first on marks this class/interface as an activity, the second one marks the activity method. Our activity consists of one method, which accepts two string arguments. The implementation of this interface is a very straight forward - just compose a new string of provided arguments:


class GreetingActivity implements GreetingActivityInterface
public function composeGreeting(string $greeting, string $name): string
return $greeting . ' ' . $name;

Both workflow and activity code in our example have both interface and implementation. But we could skip interfaces and just mark classes with corresponding attributes and everything will continue working. But how does the workflow client know about interface implementations? How does Temporal know what PHP class should be executed?

Roadrunner and Temporal Worker

To answer this question we need to take a look at how an instance of WorkflowClientInterface is created. This is the part where RoadRunner comes into a play.

In our example under the hood RoadRunner executes worker.php script:


use Temporal\SampleUtils\DeclarationLocator;
use Temporal\WorkerFactory;

ini_set('display_errors', 'stderr');
include "vendor/autoload.php";

// finds all available workflows, activity types and commands in a given directory
$declarations = DeclarationLocator::create(__DIR__ . '/src/');

// factory initiates and runs task queue specific activity and workflow workers
$factory = WorkerFactory::create();

// Worker that listens on a task queue and hosts both workflow and activity implementations.
$worker = $factory->newWorker();

foreach ($declarations->getWorkflowTypes() as $workflowType) {
// Workflows are stateful. So you need a type to create instances.

foreach ($declarations->getActivityTypes() as $activityType) {
// Activities are stateless and thread safe. So a shared instance is used.

// start primary loop

You may consider this script as a bridge between your PHP application and Temporal. Temporal needs to know about our activity and workflow implementations. Thus, they need to be registered within the worker with registerWorkflowTypes() and registerActivity(). The first one registers workflows and accepts a list of classes:


The second one registers activities and accepts a list of activity classes, e.g.:


On the last line of the worker script we start the worker. From now, it starts communication with Temporal: receiving and sending data.


Let's recap what was done in this "Hello world" example:

  1. The main script, that instantiates an instance of WorkflowClientInterface, creates a workflow and starts it.
  2. Workflow code.
  3. Activity code.
  4. Worker code with RoadRunner, that instantiates the worker, registers workflow types and activity implementations.

These reflect the 4 main APIs of Temporal's PHP SDK.