> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/tokens/using-the-created-by-token.md). # Using the "Created by" Token At SprintHub, you have access to a variety of Tokens to customize the title of an Opportunity or fill in fields with relevant information. Among them, the “Created by” Token stands out, as it allows you to identify the origin of the Lead or Company in your automations or fields. This makes it easier and more efficient to track where your Leads or Companies were created. TOKEN **LEAD -** `{contactfield=createdByName}` **COMPANY -** `{contactfield=companyCreatedByName}` {% embed url="" %} **CONCLUSION** Using the “Created by” Token in SprintHub offers several advantages for managing your opportunities. With it, you can accurately identify the origin of each Lead, making it easier to monitor and analyze your lead generation strategies. This contributes to more efficient management, allowing targeted adjustments to maximize results. In addition, automating this information saves time and reduces manual errors, ensuring a more agile and reliable workflow. In short, using the “Created by” Token enhances the organization and effectiveness of your sales actions. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/strategies/tokens/using-the-created-by-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.