Skip to main content
objectLead

Fields

assignee

The team member responsible for this lead now: its follow-ups and where it moves on the board. Separate from the closer and setter of each call, which never change when a lead is handed over. A new lead takes the closer of its first booking, when that closer is on your team. Null when nobody is assigned.

attribution

Every attribution parameter this lead's URLs carried. Provider-specific keys can appear without a schema version change.

Call records for this lead, including booking intents and scheduled bookings

Supports filtering and pagination. Returns a connection for Relay-style pagination.

Arguments
args
company
String

Company name

completedCallCount

Number of completed calls

Every consent box and what the person chose, in the order they were recorded. This includes Aura's own box for appointment texts, and STOP replies. agreed is true only while they agree for the lead's current phone number.

An empty list means no consent is on file: that is not the same as declined, but treat it as no consent. A box they did not tick is only recorded once they finish the form. Consent can change after you read it, for example when the person replies STOP, so read the lead again right before you text them. The phone number is sent either way.

consentByType

One answer for each kind of message: booking texts, marketing texts, marketing emails and data use. Each answer is yes, no or not_asked, with when it last changed. Your team chooses which consent box asks about each kind, in Settings. Booking texts can also come from Aura's own box for appointment texts. not_asked means nothing the guest answered asks about that kind yet. Answers can change later (for example, the guest replies STOP), so check again right before you send.

createdAt
String!

When lead was created

daysSinceCreated

Days since lead was created

disqualificationData

Why this lead was disqualified during booking: the form-field state and the ruleset that fired. Null when the lead was not disqualified.

doNotContact

Whether your team has blocked this person in Aura: DNC (send them no calls, texts or emails; they can still book) or BLOCKLIST (the same, and Aura also stops them from booking). Null when they are not blocked. It counts a block on this lead and a block on any other lead with the same email (a +tag is ignored) or the same phone number, so a new record for a blocked person reads as blocked too. If more than one applies, you get the stricter one. Check it before your own automations reach out to them. Who blocked them, when and why stay in Aura. If Aura cannot read it, the field is null with an error in errors.

email
String

Email address

hasScheduledCall
Boolean!

Whether lead has any scheduled call in the future

id
String!

Unique identifier

lastPaymentAt
String

When this lead most recently paid. Null if they never have.

latestCall

Most recent call

missingCurrencyRevenue

Raw settled-payment amounts with no recorded currency. These amounts cannot be added to a currency total.

name
String

Full name

nextCall

Next scheduled call

notes
[Note!]!

Additional notes about the lead

paymentCount

How many payments this lead has made.

paymentStatus
String

Rolled-up payment state for this lead. Two values are emitted: partial once any payment has been recorded, and pending before the first one or after refunds return the total to zero. It does NOT report whether a deal is paid in full — Aura has no expected total to compare against — so do not treat partial as a shortfall. Use total_paid_cents for the amount. Denormalised on the row; payments remains the authoritative edge.

Payments made by this lead

Arguments
args
phone
String

Phone number

pipelineStage

The column the lead is in on the Opportunities board right now, worked out from its calls each time you read it. Use this to show where a lead stands. status is a stored value that can lag behind: when a guest confirms a call, pipelineStage is confirmed at once, while status can still be booked until Aura's status sync updates it. The same value as stage on the lead's opportunities. For up to an hour after a disqualification rule changes, it can differ from the board, which applies the new rule on its next sync. Null only if Aura could not read the lead's calls.

revenueByCurrency
[Money!]!

Settled payment totals grouped by currency. No exchange rates are applied.

Lead source attribution (UTM params, referrer)

status

Current status in sales funnel

timezone
String

Lead's timezone (e.g., "America/New_York")

totalRevenue
deprecated

Total revenue from this lead across all payments

Use revenueByCurrency. This field returns MIXED_CURRENCY when more than one currency is present.
updatedAt
String!

When lead was last updated