A card source simply explains how a card was created and where it originated. Sources can include your Property Management System (PMS), a form submission, an email, an integration, or another board’s workflow.
To trace an existing card, see Find where a card was created . To choose how new cards enter your board, use the options below.
Add a card manually
Create a card yourself when you need to start a one-off piece of work. The board’s Start Card layout determines which fields you see during creation.
Example: Add an owner lead after a phone conversation and enter the details your team needs to follow up.
Set up the creation form: Customize card views
Collect information through forms or email
Forms
A configured Aptly form can create a card and map submitted information to card fields. Forms can be embedded on a website or shared by link.
Example: An owner completes your lead-intake form, giving your team a card with the submitted contact and property details. Forms also support resident onboarding, vendor intake and internal requests.
Setup: Using Forms in Workflows
Board email and parsers
A board email address receives messages. An email parser extracts information from recognized message formats. These work together, but they are not the same feature: card creation and populated fields depend on the board’s email settings and whether a parser matches.
Example: A rental inquiry reaches the board’s address; a matching parser extracts the prospect’s contact details and property of interest. Check the resulting card if anything is missing. The same approach can support maintenance or owner inquiries when a suitable parser is configured.
Setup: Use a board email address and Using Email Parsers
Start work from existing records
Property management data
A PMS connection brings supported portfolios, buildings, units and leases into Locations, and people such as owners, residents and vendors into Contacts. Those records can provide the starting point for configured board workflows and automations.
Example: Use a synced lease to start renewal work instead of re-entering its property and resident information.
Another board
A Create Card Rule can create a related card on a destination board when source records match your criteria. For one-off work, you can also copy a card manually.
Example: A lease approaching its end date creates a card on Lease Renewals. A configured workflow may then create separate owner- and tenant-renewal work. Copying keeps the original record in place; it is not the same as moving it.
Connect other apps — advanced
API
Developers can use the Aptly API to create cards from external systems, such as a custom work-order tool or CRM. API access requires a Premium subscription.
Example: Your in-house maintenance system sends a new request to an Aptly board.
Setup: Connect to Aptly’s API
Zapier
Zapier connects supported triggers and actions between apps without custom development. Use the invitation link in the setup guide to access Aptly’s Zapier integration.
Example: Configure a supported form-submission trigger to create a lead card in Aptly.
What a source does—and does not—tell you
A source identifies how a card originated. It does not guarantee that a sync succeeded, every field is current, or later changes will write back to another board or PMS. Supported data, update direction and write capabilities depend on the connection and configuration; check the source record and resulting card.
