Tokens are a really powerful way to reference data across Táve. They represent links to specific fields of data attached to either a job or a contact profile.  You can add them to emails, questionnaires, and contracts. Or you can reference them in Automations. They’re pretty amazing, actually.

Below is a complete list of all the tokens available. Keep in mind that since you can create custom fields (Settings > Account Setup > Custom Fields), you can create even more tokens to use, so this is not really a full list since the possibilities are endless!

IMPORTANT: In order for your tokens to render properly they need to be put into double curly brackets. So if you want to use the token job.name it must appear as {{job.name}}. Fortunately, Táve does this for you when you add tokens from the tokens button in text fields.

Brand tokens:

Táve users can have one or several brands under their account. (For example, they may have a boutique photography business and a separate one for an event photo booth). These brands can be setup under Settings > Account Setup > Branding.  Below are the tokens related to those specific brands. Add these to places like contracts or emails when you want to include any of the information referenced.

{{brand.client_portal_linked}}
{{brand.client_portal_url}}
{{brand.email}}
{{brand.email_signature}}
{{brand.id}}
{{brand.location}}
{{brand.name}}
{{brand.office_hours}}
{{brand.phone_label_1}}
{{brand.phone_label_2}}
{{brand.phone_label_3}}
{{brand.phone_number_1}}
{{brand.phone_number_2}}
{{brand.phone_number_3}}
{{brand.primary_website}}

Job tokens:

Job tokens reference almost every aspect of a specific job from the job’s name (job.name) to guest count (job.guest_count) to job financials. Let’s say you wanted to send an email to a second photographer. You could create a template email (Settings > Template Items > Email Templates) and include the job’s name, the job’s location and address, and the job’s subjects. This saves a ton of time from having to type everything out over and over again.

{{job.access_key}}
{{job.balance}}
{{job.bcc_address}}
{{job.booking_date}}
{{job.clients}}
{{job.clients.first_names}}
{{job.clients.last_names}}
{{job.clients_customers}}
{{job.clients_customers.first_names}}
{{job.clients_customers.last_names}}
{{job.clients_subjects}}
{{job.clients_subjects.first_names}}
{{job.clients_subjects.last_names}}
{{job.clients_team}}
{{job.clients_team.first_names}}
{{job.clients_team.last_names}}
{{job.closed}}
{{job.closed_date}
{{job.closed_reason}}
{{job.completed_date}}
{{job.credit_balance}}
{{job.custom.[custom-field-token]}}
{{job.custom_number}}
{{job.customers}}
{{job.date}}
{{job.date_long}}
{{job.everyone}}
{{job.everyone.first_names}}
{{job.everyone.last_names}}
{{job.fulfillment_date}}
{{job.guest_count}}
{{job.id}}
{{job.inquiry_date}}
{{job.last_client_activity}}
{{job.lead_confidence}}
{{job.lead_decision_date}}
{{job.lead_max_budget}}
{{job.lead_rating}}
{{job.lead_status}}
{{job.lead_status_changed}}
{{job.name}}
{{job.name_only}}
{{job.next_interaction_date}}
{{job.pinned}}
{{job.previous_interaction_date}}
{{job.religion}}
{{job.source}}
{{job.stage}}
{{job.stale_date}}
{{job.subjects}}
{{job.team}}
{{job.total}}
{{job.subtotal}}
{{job.total_cost}}
{{job.type}}
{{job.vendors}}
{{job.web_lead}}

Primary Session tokens:

Primary session tokens relate specifically to the event on a job’s schedule that is marked as the primary session. In the case of a wedding for example, the primary session is typically the actual wedding day event.

{{primary_session.all_day}}
{{primary_session.attendees}}
{{primary_session.attendees_clients}}
{{primary_session.attendees_clients_subjects}}
{{primary_session.attendees_subjects}}
{{primary_session.attendees_team}}
{{primary_session.confirmed}}
{{primary_session.duration}}
{{primary_session.end}}
{{primary_session.end_date}}
{{primary_session.end_date_long}}
{{primary_session.end_time}}
{{primary_session.id}}
{{primary_session.location.address}}
{{primary_session.location.email}}
{{primary_session.location.name}}
{{primary_session.location.phone}}
{{primary_session.map_link}}
{{primary_session.map_url}}
{{primary_session.name}}
{{primary_session.start}}
{{primary_session.start_date}}
{{primary_session.start_date_long}}
{{primary_session.start_time}}
{{primary_session.sunrise}}
{{primary_session.sunset}}
{{primary_session.type_kind}}
{{primary_session.type_name}}

Event Type tokens:

Your event types are set up under Settings > Lists > Event Types. These could be Call, Session, Meeting, Wedding, Engagement Session, Ordering Session. You basically can create whatever event type you’d like. Once you do, these are the tokens that are associated with that specific event type. For example, if I have an event type called Ordering Session and I wanted to send an email with a list of everyone who is attending that event, my token to include in the email would be {{ordering_session.attendees}}. I could also add {{ordering_session.location.name}} and {{ordering_session.location.address}}. Check out all the tokens that can go along with specific events:

{{[event-type-prefix].all_day}}
{{[event-type-prefix].attendees}}
{{[event-type-prefix].attendees_clients}}
{{[event-type-prefix].attendees_clients_subjects}}
{{[event-type-prefix].attendees_subjects}}
{{[event-type-prefix].attendees_team}}
{{[event-type-prefix].confirmed}}
{{[event-type-prefix].duration}}
{{[event-type-prefix].end}}
{{[event-type-prefix].end_date}}
{{[event-type-prefix].end_date_long}}
{{[event-type-prefix].end_time}}
{{[event-type-prefix].id}}
{{[event-type-prefix].location.address}}
{{[event-type-prefix].location.email}}
{{[event-type-prefix].location.name}}
{{[event-type-prefix].location.phone}}
{{[event-type-prefix].map_link}}
{{[event-type-prefix].map_url}}
{{[event-type-prefix].name}}
{{[event-type-prefix].notes}}
{{[event-type-prefix].start}}
{{[event-type-prefix].start_date}}
{{[event-type-prefix].start_date_long}}
{{[event-type-prefix].start_time}}
{{[event-type-prefix].sunrise}}
{{[event-type-prefix].sunset}}
{{[event-type-prefix].type_kind}}
{{[event-type-prefix].type_name}}

Job Role tokens:

In Táve, contacts can have job specific Roles. These are set up under Settings > Lists > Job Roles. Once you’ve set up which Job Roles you want contacts to have, you can pull their information by using the following tokens. For example, if I have a Job Role called Bride, then I would simply use the token {{bride.first_name}} and {{bride.last_name}} to add her name to where ever I place the token. If you have a contract, add the tokens in there and you can have customized contracts every single time.

{{[job-role-prefix].address}}
{{[job-role-prefix].anniversary}}
{{[job-role-prefix].balance}}
{{[job-role-prefix].best_day_to_call}}
{{[job-role-prefix].best_time_to_call}}
{{[job-role-prefix].birthday}}
{{[job-role-prefix].cell_phone}}
{{[job-role-prefix].class_of}}
{{[job-role-prefix].company_name}}
{{[job-role-prefix].contact_preference}}
{{[job-role-prefix].custom.[custom-field-token]}}
{{[job-role-prefix].email}}
{{[job-role-prefix].facebook}}
{{[job-role-prefix].facebook_url}}
{{[job-role-prefix].fax}}
{{[job-role-prefix].first_name}}
{{[job-role-prefix].gender}}
{{[job-role-prefix].greeting}}
{{[job-role-prefix].home_phone}}
{{[job-role-prefix].honorific}}
{{[job-role-prefix].id}}
{{[job-role-prefix].instagram_url}}
{{[job-role-prefix].job_title}}
{{[job-role-prefix].kind}}
{{[job-role-prefix].last_name}}
{{[job-role-prefix].maiden_name}}
{{[job-role-prefix].mailing_address}}
{{[job-role-prefix].mailing_list}}
{{[job-role-prefix].name}}
{{[job-role-prefix].pinned}}
{{[job-role-prefix].portal_linked}}
{{[job-role-prefix].portal_url}}
{{[job-role-prefix].revenue}}
{{[job-role-prefix].salutation}}
{{[job-role-prefix].school_name}}
{{[job-role-prefix].sport}}
{{[job-role-prefix].tags}}
{{[job-role-prefix].team_name}}
{{[job-role-prefix].team_position}}
{{[job-role-prefix].toll_free}}
{{[job-role-prefix].twitter}}
{{[job-role-prefix].twitter_url}}
{{[job-role-prefix].url}}
{{[job-role-prefix].vendor_type}}
{{[job-role-prefix].work_phone}}

Recipient tokens:

Recipient tokens are used specifically during the creation and sending of an email. If you’re sending the same email to multiple recipients, these tokens will populate with their respective recipients information.

{{recipient.address}}
{{recipient.anniversary}}
{{recipient.balance}}
{{recipient.best_day_to_call}}
{{recipient.best_time_to_call}}
{{recipient.birthday}}
{{recipient.cell_phone}}
{{recipient.class_of}}
{{recipient.company_name}}
{{recipient.contact_preference}}
{{recipient.email}}
{{recipient.facebook}}
{{recipient.facebook_url}}
{{recipient.fax}}
{{recipient.first_name}}
{{recipient.gender}}
{{recipient.greeting}}
{{recipient.home_phone}}
{{recipient.honorific}}
{{recipient.id}}
{{recipient.instagram}}
{{recipient.instagram_url}}
{{recipient.job_title}}
{{recipient.kind}}
{{recipient.last_name}}
{{recipient.maiden_name}}
{{recipient.mailing_address}}
{{recipient.mailing_list}}
{{recipient.name}}
{{recipient.pinned}}
{{recipient.portal_linked}}
{{recipient.portal_url}}
{{recipient.revenue}}
{{recipient.salutation}}
{{recipient.school_name}}
{{recipient.sport}}
{{recipient.tags}}
{{recipient.team_name}}
{{recipient.team_position}}
{{recipient.toll_free}}
{{recipient.twitter}}
{{recipient.twitter_url}}
{{recipient.url}}
{{recipient.vendor_type}}
{{recipient.work_phone}}

Item tokens:

Item tokens are used in reference to the attached item. For example, if you’re sending a questionnaire to your client by using a Questionnaire Invitation email template, {{item.name_link}} will be replaced by a link to the actual questionnaire.

{{item.description}}
{{item.link_end}}
{{item.link_start}}
{{item.link_url}}
{{item.name}}
{{item.name_link}}

Quote tokens:

Quote tokens are associated with, as you might have guessed, specific data related to a quote attached to a job lead. Want to write a quick email to your potential client and remind them until when their quote will be available? Simply plugin the token like this: “You have until {{quote.expiration_date}} to accept the quote before it expires. Act quickly!”

{{quote.booked_total}}
{{quote.expiration_date}}
{{quote.expiration_period}}
{{quote.id}}
{{quote.intro}}
{{quote.max_total}}
{{quote.max_subtotal}}
{{quote.min_total}}
{{quote.min_subtotal}}
{{quote.name}}

Order tokens:

Order tokens are related to a booked order. Use them in order receipt emails to summarize what they purchased and how much they paid.

{{booked_order.id}}
{{booked_order.name}}
{{booked_order.number}}
{{booked_order.summary}}
{{booked_order.products_summary}}
{{booked_order.total}}
{{booked_order.subtotal}}

Invoice tokens:

Invoice tokens are great for pulling information specific to an invoice. You can use them in emails like this:

“This is just a friendly message to let you know that you have an invoice for {{invoice.balance}} due on {{invoice.due_date}} ({{invoice.due_period}}).”  The recipient of the email will see: “… $500 due on 12/1/2014 ( in 8 days).” Just like magic.

{{invoice.balance}}
{{invoice.due_date}}
{{invoice.due_period}}
{{invoice.id}}
{{invoice.number}}
{{invoice.order_date}}
{{invoice.order_period}}
{{invoice.payment_details}}
{{invoice.response}} (payment promise response when client uses offline payment method)
{{invoice.total}}

Payment Schedule tokens:

Payment schedules are made when you’re putting together a proposal. Once a client has accepted a payment schedule why not automatically add it to the contract with words like: “You agree to pay photographer with the following payment schedule: {{payment_schedule.summary_list}}.”

{{payment_schedule.id}}
{{payment_schedule.final_amount}}
{{payment_schedule.final_date}}
{{payment_schedule.retainer}}
{{payment_schedule.summary_list}}
{{payment_schedule.summary_text}}

Contract tokens:

Add the initials box next to any place in the contract where you would like the client to add their initials.

{{contract.booked_order_summary}}
{{contract.booked_products_summary}}
{{contract.initials_box}}
{{contract.name}}

Payment tokens:

Payment tokens will give you the data associated with the actual payment a client made on an order. Include these in an order receipt along with any order tokens.

{{payment.amount}}
{{payment.auth_code}}
{{payment.memo}}
{{payment.payer}}
{{payment.received}}
{{payment.summary_box}}
{{payment.transaction_id}}

Táve tokens:

Táve tokens encompass more system wide information. It’s unlikely that you’ll use these often. However, you may find yourself using {{tave.today}} to update a field with today’s date in an automation.

{{tave.app}}
{{tave.currency.abbr}}
{{tave.currency.symbol}}
{{tave.next_year}}
{{tave.previous_year}}
{{tave.today}}
{{tave.today_long}}
{{tave.visitor.hostname}}
{{tave.visitor.ip}}
{{tave.year}}

Did this answer your question?