You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context propagators pass custom key-value data (such as tracing IDs, tenant IDs, or auth tokens) across Workflow, Activity, and Child Workflow boundaries via Temporal headers. See [Context Propagation](/encyclopedia/context-propagation) for details on how they work.
788
+
789
+
Propagators registered via a Plugin are appended to any propagators already set by the user or by previous plugins.
description: Pass custom key-value data across Workflow, Activity, and Child Workflow boundaries using Temporal headers.
6
+
toc_max_heading_level: 4
7
+
keywords:
8
+
- context propagation
9
+
- context propagators
10
+
- headers
11
+
- tracing
12
+
- observability
13
+
tags:
14
+
- Concepts
15
+
- Observability
16
+
---
17
+
18
+
Context propagation lets you pass custom key-value data from a Client to Workflows, and from Workflows to Activities and Child Workflows, without threading values through every function signature.
- Passing tenant IDs for multi-tenant applications
24
+
- Forwarding auth tokens or request-scoped metadata
25
+
26
+
Each SDK provides a **context propagator** interface you implement to control which values are injected and extracted. You register propagators on the Client, and the SDK calls them automatically at every boundary.
description: Temporal offers mechanisms to augment the functionality of Workflows and Activities, including data conversion, context propagation, interceptors, and plugins.
6
+
toc_max_heading_level: 4
7
+
keywords:
8
+
- extensibility
9
+
- interceptors
10
+
- context propagation
11
+
- data conversion
12
+
- plugins
13
+
tags:
14
+
- Concepts
15
+
---
16
+
17
+
Temporal offers many mechanisms to augment the functionality of Workflows and Activities.
18
+
These allow you to customize how data is serialized, propagate metadata across execution boundaries, and inject cross-cutting behavior like tracing and logging.
19
+
20
+
-[Data Conversion](/dataconversion) - Customize how arguments and return values are serialized, compressed, or encrypted
21
+
-[Context Propagation](/encyclopedia/context-propagation) - Pass custom metadata (tracing IDs, tenant IDs, auth tokens) across Workflow, Activity, and Child Workflow boundaries
22
+
-[Interceptors](/encyclopedia/interceptors) - Add cross-cutting behavior (observability, authorization, header manipulation) before and after SDK operations
23
+
-[Plugins](/encyclopedia/plugins) - Bundle interceptors, context propagators, data converters, and built-in definitions into reusable packages
description: Add cross-cutting behavior like observability, authorization, and header manipulation before and after SDK operations.
6
+
toc_max_heading_level: 4
7
+
keywords:
8
+
- interceptors
9
+
- middleware
10
+
- observability
11
+
- tracing
12
+
tags:
13
+
- Concepts
14
+
---
15
+
16
+
Interceptors let you add cross-cutting behavior before and after SDK operations such as starting a Workflow, executing an Activity, or handling a Signal. They work like middleware: each interceptor wraps the next, forming a chain that executes around the underlying operation.
description: Bundle interceptors, context propagators, data converters, and built-in definitions into reusable packages.
6
+
toc_max_heading_level: 4
7
+
keywords:
8
+
- plugins
9
+
- simple plugin
10
+
- extensibility
11
+
tags:
12
+
- Concepts
13
+
---
14
+
15
+
A Plugin bundles multiple extensibility primitives - interceptors, context propagators, data converters, and built-in Workflow/Activity/Nexus definitions - into a single reusable package. Plugins let platform teams and library authors ship ready-made functionality that application developers can adopt with a single registration call.
16
+
17
+
Common use cases:
18
+
19
+
- AI Agent SDKs (e.g., OpenAI Agents, Pydantic AI)
0 commit comments