Glossary

Explore Meshline

Products Pricing Blog Support Log In

Ready to map the first workflow?

Book a Demo

Glossary / Evaluation and implementation guide

Payload

A payload is the structured body of data sent in an API request or webhook event, typically formatted as JSON.

It contains fields, values and metadata that determine what the receiving system can read and act on.

Payload size limits, required fields and schema shape vary by vendor, so two tools claiming the same integration can still exchange very different data.

A practical example

Example: a form submission payload might include email, company, campaign source and a custom field for deal size. If the connector drops the custom field, your routing rules that depend on it silently fail.

What to evaluate before investing

  • Ask vendors for a sample payload from each integration you plan to use, not just a field list.
  • Verify whether custom fields you rely on are included or require a premium plan or custom mapping.
  • Check documented payload size limits against your largest records, such as contacts with long activity histories.

Limitations and tradeoffs

Payloads are vendor-specific; a field present in one tool's webhook may be absent or renamed in another, requiring mapping work.

Plan your next step with MeshLine

Connect this decision to your automation, organic marketing and customer lifecycle management. In a MeshLine demo, discuss your existing tools, the scope you need and how to measure the result.