# Playbooks now support the v5 Python SDK

**URL:** <https://community.limacharlie.com/t/playbooks-now-support-the-v5-python-sdk/791>\
**Category:** Announcements\
**Tags:** extension, cli\
**Created:** [October 6, 2026, 1:48am UTC](https://community.limacharlie.com/t/playbooks-now-support-the-v5-python-sdk/791 "2026-10-06T01:48:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maximelb](https://yyz1.discourse-cdn.com/flex033/user_avatar/community.limacharlie.com/maximelb/32/13_2.png) [@maximelb](https://community.limacharlie.com/u/maximelb)\
**Post date:** [October 6, 2026, 1:48am UTC](https://community.limacharlie.com/t/playbooks-now-support-the-v5-python-sdk/791/1 "2026-10-06T01:48:32Z")

</div>

You can now write playbooks against v5 of the LimaCharlie Python SDK. Your existing playbooks keep running on v4 with no changes. To move a playbook to v5, add `sdk_version: "5"` to its `playbook` record:

```yaml
python: |
  def playbook(sdk, data):
      info = sdk.get_info()
      return {"data": {"oid": sdk.oid, "name": info.get("name")}}
sdk_version: "5"

```

With v5, the `sdk` argument is a pre-authenticated `limacharlie.sdk.organization.Organization` instead of the v4 `Manager`. If the request has no credentials, `sdk` is `None`, same as in v4. Each v5 playbook runs in its own isolated process.

A few differences from v4:

- Whatever your playbook returns must be JSON-serializable.
- `is_interactive` only works on v4. A v5 request with `is_interactive=true` is rejected.
- If you leave `sdk_version` out, leave it empty or set it to `"4"`, you get v4. Any other value returns an error.

You can migrate one playbook at a time and keep v4 and v5 playbooks running side by side in the same org.

SDK docs: [v5](https://docs.limacharlie.io/6-developer-guide/sdks/python-sdk/) · [v4](https://docs.limacharlie.io/6-developer-guide/sdks/python-sdk-v4/)