> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/repx-updates/september-14-2026.md).

# September 14, 2026

Hey Storylaners! Marketo joins the list of apps RepX integrates with. RepX conversations now land on the person record alongside everything else you track on Marketo.

### 📧 Send conversation data to Marketo 

RepX writes **conversation data** straight into Marketo, so the information shows up in the same place your nurture and scoring programs already run. 

These are new fields that are now added into Marketo for RepX related information:<br>

* Storylane RepX conversation topics
* Storylane RepX conversation at
* Storylane RepX total messages

\
**Besides, some Storylane fields now pull in data based on RepX conversations.** \
\
If you already run the Demo Suite Marketo integration, **Storylane Buying Intent** and **Storylane Lead Source** now factor in RepX conversations, not just demo and hub activity.

**A custom activity per conversation.** Each conversation logs an activity on the Marketo timeline carrying the full transcript, so your team can read what was actually said without leaving Marketo.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.storylane.io/repx-updates/september-14-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.